Skip to content
Forward Deployed

Forward Deployed
Lessons and contents
GraphRAG TechniquesLesson 1 of 6
6 lessons
Learn

GraphRAG Techniques: overview

Source
From the RAG & Agents Engineering course
By
Sourav Banerjee
Last updated
8 Nov 2026

Report an issue

Graph retrieval changes which evidence reaches the answer model. A question can start at one entity, follow a relationship to another passage, or ask for themes across communities. The T13.3 notebooks build on four ideas: community detection, global and local search, graph expansion, and the indexing work those choices require.

The running example is the fictional Larkspur Cloud handbook. “Which export mechanism remains available after cancellation?” needs a connection between policy and product pages. “What dependencies recur across cancellation, exports and outages?” asks for a corpus overview. These questions need different retrieval plans, even when they share an index.

In short

  • Decide what a node and an edge mean before calling a system GraphRAG. A similar pair of chunks, an extracted factual relation and a community membership support different inferences.
  • Local search starts near entities; global search uses community reports to cover the corpus. Choose using the question's required evidence.
  • Expansion increases the candidate set. In the lab's cancellation fixture, degree 0 returns 2 relations; degree 1 returns 4. Neither count measures answer accuracy.
  • Carry source passages through extraction, traversal and generation. A citation marker alone does not establish that its claim follows from its source.
  • Compare indexing, updates and query work on the same question set before replacing the flat retrieval baseline.

Mental model

Preserve sources before choosing a graph retrieval routeExtract a graph from passages, retain source links, then choose entity expansion or community reports for the question. PassagesSource text Extract graphEntities and relations Keep sourcesPassage and span IDs Choose routeEntity or corpus scope Local searchSeeds and adjacency Global searchCommunity reports
  1. Keep the original passages as the evidence source.
  2. Build entity and relationship records from those passages.
  3. Keep passage IDs and source spans with each extracted record.
  4. Choose the retrieval scope from the question’s evidence needs.
  5. Expand around entities or select community reports, then return source evidence.

Both routes must return evidence that the answer can cite. The graph supplies candidate connections; the source passages establish what the handbook actually says. Community reports add a summary layer whose omissions need checking against those passages.

Interactive lab

Expansion and the evidence set: open the file in a browser. Start with Cancellation and compare degrees 0 and 1. Increase the degree until the source set stops growing. Switch to Outage to see that the same expansion budget reaches different passages from a different seed.

How it connects

  • Before: T13.1 retrieves at different abstraction levels. T13.2 models and queries factual relationships. This module uses graph structure to choose evidence.
  • Next: T15.1 compares complete agentic RAG architectures, including the cost of routing and repeated retrieval.

Key Takeaways

  • Name the graph representation and retrieval route in each evaluation result.
  • Bound expansion before context construction and measure the candidate set it creates.
  • Preserve passage provenance through both graph and community retrieval.
  • Re-evaluate source coverage, update work and answer quality whenever extraction or routing changes.

Rate your confidence and keep notes on the module page.