Repository navigation
Possible use case #48
Description
Not an issue, but I don't know where else I can submit this. I love this project, and I'm considering using it for my backend. I use traditional RAG for semantic search. To use structured RAG for the whole thing would become a bit costly, but a hybrid application could be very useful:
- take the top results of the semantic search and apply structured RAG only for this subset.
- this gives me explainability of the search results, and a better overall ranking quality of the top search results.
What do you think?
Activity
gvanrossum-ms commentedon Oct 23, 2025
I think all the parts are somewhere under typeagent/knowpro (which contains the core algorithms). Search for
KnowledgeExtractor.I'd recommend caching the knowledge extracted by Structured RAG so that you incur the cost of knowledge extraction at most once per document.
I think you won't get the ultimate benefit of Structured RAG, because you are still limited by the ~60% recall that apparently plagues all vectorbases.