Export a graph with its source evidence.

For: Data and knowledge architects

Turn document facts into stable semantic objects and evidence-bound relations inside a versioned World.

A graph that cannot show why an edge exists is difficult to review, govern or trust downstream.

Input
Facts in your documents
Action
Inspect objects and evidence-bound relations
Output
Turtle, JSON-LD and CSV exports

From filing text to objects and edges.

  1. 01

    Create semantic objects

  2. 02

    Hold uncertain identities for review

  3. 03

    Bind source evidence

  4. 04

    Emit evidence-bound relations

  5. 05

    Activate a reviewed World

What loads into the store you already run.

  • Stable object and relation IDs
  • Ontology and graph exports
  • Version history and rollback
  • Evidence for every qualified edge

Check the sample

An export with inspectable evidence IDs.

From the source

Table of Contents Summary Governance Directors Compensation Proposals Other Information Nominees to Apple’s Board of Directors Apple is overseen by directors with a broad range of…

DEF 14A · filed 2026-01-08 · page 11Open this region on /explore

A proxy passage naming people and roles — the kind of region an object and its relations are compiled from, with the evidence that supports each one still attached.

graph/relationships.csv

CSV header and one emitted relation with its evidence IDs

id,subject_id,predicate,object_id,evidence_ids
"relation-6cb1b7087cd53efb3fb8dc9b59225932","document-5a70ec70f7b1a1726a25ed51a5dc716a","discusses_topic","topic-b696d75511dc16f2b52563e3113a4983","evidence-5a70ec70f7b1a1726a25ed51a5dc716a"

This row binds evidence at document level and shows the export’s shape.

Inspect the full sample package

Five public Apple filings, compiled with the TypeScript sample compiler.

WHAT TO PLAN FOR Before your first compile

The graph is compiled from documents, so an object exists only where a source region supports it.

Exports are Turtle, JSON-LD and CSV — load them into any store you already run.

An uncertain merge is never decided silently: it is held for review with the regions that support each side.

Planning a first compile? See how a design partnership works.

Next: Build on it in Resources, or the exact product contract in the documentation.