Which business relationships belong in a graph?

Enterprise information is spread across tables, documents, and operational systems. An isolated passage may state that a customer's orders declined without identifying the region, revenue definition, or data update time. A context graph links the customer, orders, region, metric definition, and evidence source, allowing an application to follow an explicit path instead of relying only on text similarity.

How does it connect entities to evidence?

Nodes may represent customers, products, devices, metrics, reports, policies, and people. Edges may mean “belongs to,” “calculated from,” “cites,” “owned by,” or “governed by.” Recording the source, effective date, and owner of each important relationship helps make it verifiable. When a question arrives, the system identifies relevant entities, traverses limited relationship paths, and filters candidates by user permissions and task. The agent receives selected context rather than the entire graph.

In device troubleshooting, a device ID may connect recent alerts, maintenance tickets, manuals, and the responsible team. The graph can show which alert relates to which repair, while live device status must still be read from the operational system. Stale relationships can repeatedly mislead answers, so the graph needs updates and quality checks. How MIP helps AI understand your business discusses the broader role of business relationships in AI context.

“Context graph” is not a single standardized architecture. It often describes a knowledge graph used to supply task specific context to an AI application. Knowledge graphs emphasize modeling entities and relations; a context graph emphasizes selecting relevant relations, sources, and governance information for a task. Vector search can discover semantically similar text, while graph traversal follows explicit connections. A system may use search to find candidate nodes and graph relationships to check them. Simple question answering may not need a graph. See also the AI context layer.

FAQ

Does a context graph require a graph database?

No. Relationships can also be stored in relational tables or indexes. Complex traversal requirements may influence the storage choice.

Can a graph eliminate hallucinations?

No. It offers inspectable relationships and sources, but extraction errors, stale data, and reasoning mistakes remain possible.

Where should a team start?

Choose one valuable use case with meaningful relationships. Define core entities, authoritative sources, and update owners, then test graph paths with real questions.