R127 · Knowledge for agents › Retrieval over long documents

GraphRAG Zero: graph-guided retrieval with no LLM calls at index time

Read the original

retrievalragknowledge-graphsevalsmemory

Source: Microsoft Research, The evolution of GraphRAG: advancing systems and evaluation together (2026-11-17), announced on LinkedIn. GraphRAG Zero ships as an option in Foundry IQ (Azure AI Search) and inside GitHub Next's Repo Mind Light. The research numbers below come from Microsoft's own study and, as the post says, are not measurements of the hosted service.

Three generations

What the evaluation adds

The story is as much about measurement as retrieval. BenchmarkQED, Microsoft's open-source suite, generates questions (AutoQ) from a dataset or from representative user activities, at local or global scope, and now also generates source-grounded assertions: testable statements an answer should contain. Retrieval is scored separately from writing quality: chunk precision from LLM relevance judgments, and a cluster recall that measures topical breadth rather than document recall.

In the GraphRAG Zero study (podcast transcripts and news, 200 synthetic questions split between multi-hop and global, 50-chunk budget, same embedder and answer model): global answer assertion coverage rose from 53.4% with vector RAG to 57.4%, with context prepared in 0.93 seconds on average. GraphRAG Zero had higher cluster recall and topical fidelity; vector RAG kept higher chunk precision. The lesson the authors draw: precision alone would have steered development the wrong way, because more representative evidence produced more complete global answers.

Evaluation for agent loops

For agents whose knowledge changes as they work, the team scores graded evidence coverage: an LLM judges each chunk's support for each assertion as full, partial or none; the best support per assertion is averaged. Repeated evidence earns nothing; covering a missing fact does. With datasets, questions, assertions and judging held fixed, assertion-chunk judgments can be cached and reused across system versions, so each iteration only pays to judge new evidence. Microsoft frames this as part of loop engineering: improve, test against a fixed standard, repeat.

A related GitHub Next project, WikiKB, keeps repository knowledge as reviewable Markdown with provenance and Git history, indexed and retrieved locally.

Tradeoffs

Failure modes to plan for

Review checklist

Connections

See R127 on the knowledge map

Part of the Research notes on nowucca.com. Figures and claims are the source's own unless the summary says otherwise.