azure-search-openai-demo
azure-search-openai-demo copied to clipboard
Azure-Samples
GraphRAG support
This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [X] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
I just recently learned about a new RAG approach called GraphRAG, which shows impressive improvements over plain RAG: https://data.world/blog/generative-ai-benchmark-increasing-the-accuracy-of-llms-in-the-enterprise-with-a-knowledge-graph/
Microsoft already has an accelerator project here: https://github.com/Azure-Samples/graphrag-accelerator
It would be nice if this new RAG approach could be integrated into this project, although I'm not sure if it's mature enough yet.
Yes, we've seen that and even tinkered with it a bit, back before it was public. It'd help to know if developers here have tried it and seen quality improvements. If anyone else has, please comment and share!
Related: There's a session on GraphRAG at our upcoming RAGHack: https://reactor.microsoft.com/reactor/events/23432/
I've got the GraphRAG project working but have not merged it in with this project. Out of the gate, the responses seem much deeper and more concise. That being said, turning on reranking with the vector similarity model is still very strong. GraphRAG also forces us to use UTF-8 encoding which is a big change if you're using the computer vision version of this project.
Interesting, thanks for your comment. From what I see, the cost of building the graph is really the showstopper. In the first release of our app, we have about 10,000 documents in the index (~394k chunks), and we plan on adding even more documents. GPT 4o mini seems to be the cheapest option but still, from the estimates I saw, it would still be thousands to build the graph. How was the cost for you?
Indeed, cost to build the knowledge graph is high. Even more so given that, at the moment, it appears that the knowledge graph needs to be rebuilt from scratch when adding new documents.
The introduction of LazyGraphRAG could be the breakthrough needed to make GraphRAG cost-effective enough for practical implementation.
