prasmuss15

5 ms·

1. 1.▲
   by prasmuss15 2y ago

   I'm not quite sure I follow. Today, graphiti extracts entities as nodes and facts between those nodes as edges. The nodes and edges store semantic data, like summaries of entities and facts representing the relationships between them (
2. 2.▲
   by prasmuss15 2y ago

   Hey! Do you mean tips for implementing a similar project in TS? Or do you want to make a project in TS using graphiti? If you want to use graphiti in a TS project you can wrap the graphiti library in a Python server (using fastAPI, Flask or
3. 3.▲
   by prasmuss15 2y ago

   Thanks for the follow-up and the in depth example and explanation. Like you said, supporting ontologies is definitely a core use-case of KG's and there are also many standard preexisting taxonomies for different things (Google and Amaz
4. 4.▲
   by prasmuss15 2y ago

   Yes, that is in the works and is a high priority for us. The major discussion point internally around implementing this feature has been on the retrieval portion. In general we want to provide many flexible search strategies that return a v
5. 5.▲
   by prasmuss15 2y ago

   Hey, thanks for the feedback! I'm one of the devs on graphiti and adding support for custom schema is high on our to-do list. I agree that this is an important step in helping to bridge the gap between structured and unstructured data,