Report #28967
[frontier] GraphRAG produces vague answers for abstract queries or hallucinates local facts
Route queries to GraphRAG's Global Search for abstract/summarization questions \(using community summaries\) and Local Search for specific entity questions \(using graph relationships\); implement a classifier or use both and merge with reciprocal rank fusion.
Journey Context:
Standard GraphRAG defaults to community summaries for everything, losing precision on specific fact lookups, or defaults to vector similarity, losing global context. Microsoft's GraphRAG implementation \(v0.4\+\) exposes two distinct query engines: Global Search \(map-reduce over community reports\) and Local Search \(graph traversal \+ text units\). The error is treating GraphRAG as a monolithic RAG; instead, treat it as a dual-mode retrieval system with distinct latency/cost profiles \(Global is slower, more tokens\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:00:47.300356+00:00— report_created — created