Knowledge graphs in depth
A Knowledge Graph (AMPG) turns your documents into a structured graph that agents can draw on when they answer. This page follows one document through its full lifecycle — where it is uploaded, where it is processed, where the resulting graph lives, and how it is retrieved at query time — with a focus on what happens to your data and where it lives. It deliberately does not describe how the graph is produced: that construction process is proprietary. The end-user workflow is covered in Knowledge Graphs (AMPG).
What this page does and does not cover
This is a data-residency and lifecycle reference. It tells you, for an audit, exactly where your document and its derived graph reside at each stage, and that nothing leaves your account.
It does not document how AlphaAgent builds the graph — the methods that read a document and turn it into entities, relationships, and the structures used to retrieve them are intellectual property and are intentionally out of scope here. What you can rely on is the residency and handling described below.
The lifecycle of your document
1. Upload — your S3
When you add a document to a Knowledge Graph, it is uploaded to an S3 bucket in your own AWS account. The original file resides there; it is not sent to PrometheusRL.
2. Processing — in your account
Adding a document starts a build job that runs inside your account. Studio shows the job's progress as it moves through a series of visible stages, with live logs, so you can watch it advance and see when it completes or needs attention. All compute for this job runs in your account, and any model inference it uses runs on AWS Bedrock pinned to your residency zone (see Data residency and security).
What happens inside those stages — how the document's content is analyzed and how the graph is assembled — is proprietary and not documented here. What matters for residency is that it all happens in your account and your zone.
3. Storage — your Neo4j
The resulting graph is stored in your Neo4j, which lives in your account in either mode: self-hosted, where Studio runs single-node Neo4j Community on Fargate inside your VPC, backed by encrypted multi-AZ EFS; or external, your own Neo4j instance. The graph is not stored in any PrometheusRL system. Because Neo4j is in your account, the graph's storage, backup, and access controls are under your control.
4. Retrieval — at query time, from your Neo4j
When an agent uses a Knowledge Graph to answer a question (this happens in Deep Traversal mode, where the graph is consulted first), it retrieves relevant context from your Neo4j at query time. The retrieval is bounded so that only a focused amount of graph content is brought into the answer, and the agent's response can cite what it drew on. As with everything else, retrieval and the inference that uses it stay in your account and your residency zone.
The exact retrieval and ranking logic is proprietary and out of scope here; what is documented is that the source of truth is your Neo4j and that nothing about the query or the graph leaves your account.
Where your data lives, stage by stage
| Stage | Where the data is | Whose system |
|---|---|---|
| Uploaded document | S3 uploads bucket | Your AWS account |
| Build job (processing) | Compute and intermediate artifacts | Your AWS account |
| Model inference during build | AWS Bedrock, your residency zone | Your AWS account |
| Finished graph | Neo4j | Your account (self-hosted on EFS, or external) |
| Query-time retrieval | Neo4j | Your account (self-hosted on EFS, or external) |
Residency summary
- Your document never leaves your account.
- The graph is built in your account and stored in your Neo4j.
- All inference, during both build and query, runs on AWS Bedrock in your chosen residency zone.
- Nothing about your documents, the derived graph, or your queries is transmitted to PrometheusRL.
Where to go next
- Knowledge Graphs (AMPG) — building and managing knowledge graphs as an end user.
- Data residency and security — the account boundary and zone pinning that this lifecycle relies on.
- What runs in your account — where Neo4j and Bedrock sit in the overall picture.