Skip to main content

Knowledge graphs

A knowledge graph (shown as an AMPG, Augmented Multi Resolution Property Graph, in the dock and the sidebar) is what an agent grounds its answers in; each build is a version, built from one PDF, and agents pin to a version. Read this before you build or pin a graph.

How versions work​

Every build is a version with its own graph, statistics and source document. Versions are peers: each agent pins one and keeps it until you move it; where Studio needs a default it proposes the highest Ready version. A version is Building, Ready, Failed, Cancelled or, briefly, Deleting. One version of a graph builds at a time. A graph that has never been built reads "No versions yet. Build the first one from a PDF of up to 32 pages."

The list​

  1. Open AMPGs in the dock. The list (/knowledge-graphs) is headed Knowledge Graphs. A grey storage line under the heading, for example Graph storage 0.6 GB · Neo4j memory 32% · Artifacts 0.2 GB · measured 10:15, is read once when the list opens; an unmeasured value shows a dash, and the line is absent if the deployment reports nothing.
  2. Filter with Search by knowledge graph ID or name…; the pager then shows how many rows matched.
  3. Columns: Name, Description, Versions (v3 ready · v4 building, 1 version · failed or no versions yet; the list re-reads every 5 seconds while any row builds), Created and Updated. Each row offers Open, New version and Delete; the last two are disabled while a version builds ("v4 is still building").
  4. Click Create knowledge graph for a new graph; Previous and Next page. Empty: "No knowledge graphs yet." and "Create one from a PDF of up to 32 pages." No hits: "No knowledge graphs match your search".

Where to go next​

PageRead it for
Build a versionThe PDF limits, the six-step rail, the live log, cancelling, failures, Retry as new version.
Use, move agents, deleteThe graph page, the Versions table and Stats, which agents pin which version, Move N agents here, Share, deleting a version or the graph.
Agents: configure and activatePinning one agent to a Ready version.
Workflows: knowledge-graph update nodeBuilding a version from a workflow.

Notes​

RuleValue
Name and descriptionup to 100 and 500 characters
Source PDFone per version, up to 32 pages and 50.0 MB
Builds per graphone at a time
Graphs per user256 in a standard deployment ("You've reached the limit of 256 knowledge graphs."); server-enforced in a governed one
Shareneeds a Ready version
Delete graphrefused while a version builds or any agent is pinned
  • The sidebar section Augmented Multi Resolution Property Graphs shows AMPGs on the list and, inside a graph, ← All AMPGs and Details. Addresses starting /knowledge-bases open under /knowledge-graphs; older document, training and update links open the graph's page.
  • "Error loading knowledge graphs" or "We couldn't reach the Knowledge Graph service.": reload. "Studio is temporarily unavailable": Studio re-reads every 5 seconds; nothing is lost. "Studio is updating": wait, then Retry.