Skip to content

GraphRAG

πŸ“ Short definition

RAG architecture that extracts entities and relations into a knowledge graph, enabling global queries classic vector search cannot answer.

πŸ“– Detailed definition

Popularized by Microsoft research (2024), GraphRAG replaces (or complements) the vector database with a Knowledge Graph: the system extracts entities (people, places, concepts) and relations from documents. At query time, the LLM can traverse the graph for global or relational questions.

Example impossible for classic vector RAG but feasible with GraphRAG: β€œWhat cross-cutting themes appear across all product-team documents this month?”

Downside: graph construction is costlier and more complex than simple vector indexing.

πŸ’‘ Why it matters for on-prem AI

Relevant when the document base is relation-heavy (legal corpora, source code, technical docs). Prefer it when vector RAG fails on global synthesis questions.

⚠️ Common pitfalls

  • High entity-extraction cost (often needs a dedicated LLM to build the graph).
  • Harder to update than a vector index.
  • Not always better than vector RAG for localized factual lookup.

πŸ“š Go deeper

  1. 🧩 RAG & Agents (GraphRAG in the agentic evolution context)

πŸ”— See also

Give my opinion

Everything is optional: one answer is enough. This site sends nothing: you send it, the way you choose.

Your noteNo note
Your opinion is about
About what? (several choices possible)
What will be sent
Send by e-mail

Private, no account: opens your mail program with the message ready, for ia-on-prem@damien.becherini.fr.

Open a GitHub issue β†—

Public, with a GitHub account. You read the issue again before you publish it.

To paste it wherever you want.

Give at least a note, a subject or a message to be able to send.