Skip to main content
Vector search alone fails on multi-hop reasoning — corporate ownership chains, compliance lineage, cascading civic approvals, vessel-to-company-to-sanction chains. The entity graph export gives you a compact, queryable edge list you can import into your own graph layer.
The entity graph export is available on the Enterprise tier only. It ships as codex_entity_graph.parquet alongside per-dataset slices and a stats sidecar with every Enterprise catalog purchase.

What you get

A single Parquet edge-list file (Snappy-compressed) with per-dataset slices. This is not a graph database — you import it into your own graph engine (Neo4j, Kuzu, TigerGraph, DuckDB, NetworkX, or similar). Expected size at launch: approximately 8–12 million edges across all dataset families.

Edge schema

Each edge in the graph has the following fields:

Node types

Every node is addressable by a stable ID. Most use APRS URNs.

Edge types

Civic

Events

Maritime

Permits

Urban Signal Grid

OSHA

Example queries

You can query the graph directly with DuckDB and Parquet — no external graph database required.

Vessel → owner → sanctions → sister vessels

Recursive cascade — downstream records from a dark event (up to 3 hops)

Provenance

Every emitted edge carries evidence_anchor, extractor, and confidence, following the same contract as the claim/fact layer. You can join edges on source_record_id back to the record’s claims[] array for full provenance.

Tier availability