order_total doesn’t say whether it holds revenue before or after tax, or which of several similar tables your analysts rely on. Without that context, Maia Team has to work out the answer from names and structure alone. With a knowledge graph, it already knows.
This guide explains why Context Engine is useful and how knowledge graphs work. To create your first knowledge graph, read Creating knowledge graphs.
Expand this box to watch our video about Context Engine and how to use it to build and manage knowledge graphs.
Video: Unlock data insights with Context Engine
Video: Unlock data insights with Context Engine
How Context Engine helps you work more efficiently
When Maia Team has access to a knowledge graph, you can:- Ask in your own words: Use the terms your business uses, such as “revenue”, “active customer”, or “churn”, instead of naming exact tables and columns. Maia Team maps your terminology to the right data.
- Build pipelines that fit your data landscape: Maia Team builds pipelines using the tables, columns, and relationships that exist in your warehouse, rather than starting from generic assumptions.
- Get more relevant answers: Maia Team draws on your business data, semantics, and processes when it responds, so you spend less time adding background detail to your prompts and correcting its assumptions.
- Understand your data landscape: Explore your knowledge graph visually to see how business concepts, tables, columns, and pipelines relate to one another.
- Keep context up to date: Crawlers refresh your knowledge graph on a schedule you set, so it keeps pace with changes to your data.
- Share context across your team: A knowledge graph is built once and reused by everyone who has access to it, so your team works from a shared understanding of the same data.
Knowledge graphs
A knowledge graph is a map of your data and what it means. It’s made up of nodes, which are the things in your data landscape, such as tables, columns, business concepts, and pipelines. It also contains edges, which are the relationships that connect them. Every knowledge graph has two connected layers:
For example, a business concept such as “total order revenue” can link to every column across your warehouse that holds that value. When you ask Maia Team about revenue, it follows those links to find the right data. To learn more about what knowledge graphs contain and how to explore them, read Visualizing knowledge graphs.
We recommend adding all your business information to one knowledge graph, unless the data needs different regional or access requirements. For more information, read Decide whether to create a new graph.
Accessing Context Engine
The Context Engine dashboard shows all the knowledge graphs you can access or request access to. Use the Projects drop-down to filter the displayed knowledge graphs by project, or use the search field to search for a knowledge graph by name or description. Access to knowledge graphs depends on your role:- By default, only users who have an account role with the Create knowledge graph permission can create and edit knowledge graphs and crawlers. However, all users can request contributor access to edit specific knowledge graphs.
- All users can select knowledge graphs when creating tasks in Mission Control, and Maia Team will automatically use knowledge graphs in chats with all users if they enable Context Engine in chats.
Work with knowledge graphs
Creating knowledge graphs
Create your first knowledge graph and run its first crawl.
Managing knowledge graphs
Configure crawlers, upload documents, and manage access to your knowledge graphs.
Visualizing knowledge graphs
Explore the nodes and relationships in your knowledge graphs.