Knowledge Graph

Akurion Graph RAG builds project-level entities and relationships from processed file evidence. It helps the platform answer relationship-heavy questions and gives users another way to explore knowledge beyond keyword or vector search.

What the Graph Stores

Graph RAG uses these concepts:

Concept	Meaning
Node	An entity such as a product, system, customer, person, policy, vendor, or application.
Edge	A relationship between two nodes.
Alias	Alternate names for a node.
Evidence	Source file, page, excerpt, and metadata supporting a node or edge.
Build run	A record of graph extraction or rebuild activity.
Review item	A candidate issue or ambiguity needing human review.
Suppression rule	A rule that blocks unwanted graph relationships.

When to Enable Graph RAG

Enable Graph RAG when your users ask questions like:

“Which systems are connected to this application?”
“What documents mention this vendor and related risks?”
“Which incidents relate to this product area?”
“Show relationships between policies, controls, and evidence.”
“What customers are associated with this issue?”

How Graph RAG Helps

Graph RAG adds relationship awareness to project knowledge:

Surfaces important entities and how they relate.
Connects answers to supporting evidence.
Helps users explore systems, policies, vendors, customers, and risks as a connected map.
Gives admins review controls for relationship quality.
Improves answers when a question depends on context across multiple sources.

Admin Controls

Project admins can:

Enable or disable Graph RAG.
Rebuild the full project graph.
Rebuild one file graph.
Remove graph state for a file.
Clear the project graph.
Create, update, or delete nodes.
Create, update, or delete edges.
Add or delete aliases.
Create or delete suppression rules.
Resolve review queue items.

Graph in Retrieval

When Graph RAG is enabled, advanced answers can use relationship context alongside document evidence. This helps answers explain not only what a source says, but how entities, systems, policies, or records relate to each other.

Developer Access

Graph management is available through the Akurion app for authorized admins. Public API documentation focuses on stable developer surfaces; source-specific or internal graph operations are documented only when they are intended for external use.

Best Practices

Start with a focused project before enabling graph extraction over very large corpora.
Define useful metadata keys before graph builds.
Review low-confidence entities and relationships.
Use aliases for common abbreviations and alternate names.
Use suppression rules for noisy or misleading relationship patterns.
Rebuild after major metadata or source-scope changes.