Mirofish graph shows all entities as "extractedentity" instead of correct entity type.

[Benniepie]

In Mirofish the generated entity types created during ontology are not being handled by properly , instead all entity types are returned as "extractedentity" (see your own screenshot of the graph from Mirofish - there should be a variety of different entity types not just the one type (all orange on graph).

[N1nEmAn]

This should be fixed on main.

Root cause:
OpenZep was accepting MiroFish ontology requests, but it was not actually applying the ontology during extraction. As a result, extracted nodes fell back to the default compatibility label (ExtractedEntity) instead of using the dynamic entity types generated by MiroFish.

What was changed:

• PUT /api/v2/entity-types now actually registers the ontology instead of acting like a stub.
• graph.add / graph.add_batch now pass the registered ontology into Graphiti extraction.
• Compatibility was added for looser OpenAI-compatible providers that:
  • return fenced JSON
  • return arrays instead of wrapped objects
  • use fields like entity_name / entity_type_name
• If the provider does not expose /v1/embeddings, OpenZep now falls back to a deterministic local embedding so graph construction can still complete.

I also tested this from the MiroFish side, not just inside OpenZep.

Result from the MiroFish integration test:

• node_count = 3
• edge_count = 2
• labels:
  • Alice -> Student
  • Bob -> Student
  • Peking University -> University

So the graph is no longer collapsing everything into ExtractedEntity.

Relevant fixes were pushed to main, including:

• ontology registration and application
• null-compatible ontology request handling
• tolerant LLM / embedding provider compatibility

If you pull the latest main and rebuild / restart OpenZep, MiroFish-generated ontology types should now show up correctly in the graph.

[Benniepie]

Thank you for coming back to me so quickly and for fixing the issue - I can confirm it's working exactly as you stated - The ontology entity types , the map & legend all now agree & display correctly!
Thank you for providing a non-SaaS alternative to Zep!

[N1nEmAn]

Thank you for coming back to me so quickly and for fixing the issue - I can confirm it's working exactly as you stated - The ontology entity types , the map & legend all now agree & display correctly!
Thank you for providing a non-SaaS alternative to Zep!

Hey Benniepie!

Thanks so much for confirming that the OpenZep setup works reliably for you! 😊

Since you’ve got it running smoothly, I was wondering if you’d be open to writing a detailed technical blog post about the full setup process when you have some extra time. I’ve noticed a lot of other users are running into weird edge-case issues that I can’t always reproduce on my end, so a step-by-step guide from someone who’s successfully implemented it would be incredibly helpful for the community.

No pressure at all—just thought I’d ask! Thanks again for testing this out and sharing your experience.

[N1nEmAn]

Thank you for coming back to me so quickly and for fixing the issue - I can confirm it's working exactly as you stated - The ontology entity types , the map & legend all now agree & display correctly!
Thank you for providing a non-SaaS alternative to Zep!

Also, could you let me know which commit hash you’re using?
I’d like to use that working commit to make a proper release, in case my recent changes caused some unexpected issues.

Thanks a lot!