D·bridge Domain Layer Enter the demo

Insurance knowledge graph / Phase 0 demo

Answers you
can defend.

D·bridge resolves your policies, claims, and parties into one canonical graph — so an underwriting question gets a plain-language answer, traced to every source document behind it.

Enter the demo Watch a question resolve ↓
Standard
ACORD-aligned
Provenance
PROV-O lineage
Every answer
cited & traceable
lineage trace ClaimFile · CLM-4471
question ClaimFile Coverage C Customer ClaimPayment Policy Claimant CaseReserve policy.pdf fnol.xml ledger.xml

    entities
    —
    dq issues
    —
    lineage depth
    —

    how it works

    From filing to answer

    Three stages, one direction. Source-shaped records become a canonical graph you can interrogate — and every transformation stays on the record.

    1. 01

      Ingest

      Policies, claims, and ACORD filings land exactly as the source systems shaped them — XML, PDF, and everything in between. 

      acord_fnol.xml
<Claim claimNo="CLM-4471">
  <Insured>ACME Logistics Ltd</>
  <Loss peril="Water"
        date="2026-03-02"/>
</Claim>
    2. 02

      Resolve

      Duplicates and aliases collapse into canonical entities. Every link carries a confidence score; data-quality mismatches are flagged, not hidden.

      canonical entity

      ACME Logistics Ltd

      Customer · resolved from 3 records match 0.94

    3. 03

      Answer

      Ask in plain English. The answer is grounded only in this claim’s graph, its DQ findings, and its lineage — and it arrives with citations attached.

      grounded answer

      Coverage C (Water Damage) is in force on POL-88231.

      ↳ policy.pdf · §Coverage C

    entity resolution

    Three records.
    One company.

    Brokers, policy admin, and claims each spell the insured a little differently. D·bridge folds them into a single canonical entity — and keeps the confidence and the evidence so a steward can always check the seam.

    See it merge in the demo →
    • ACME Logistics Ltdfnol.xml
    • Acme Logistics Limitedpolicy.pdf
    • ACME LOG. LLCbroker.pdf
    Customer

    ACME Logistics Ltd

    3 records · confidence 0.94

    provenance

    Every answer carries its receipts.

    Behind each answer is a PROV-O trail: the property value, the object snapshot it came from, and the source file it was derived from. Nothing is asserted that can’t be walked back to a document.

    “Is water damage covered under this policy?”

    Yes — Coverage C is in force, sub-limit $250,000.

    1. property_value coverage.inForce = true
    2. object_snapshot Coverage C · POL-88231
    3. file policy.pdf · §Coverage C

    prov·WAS_DERIVED_FROM · depth 4

    governance

    Built for people who get audited.

    Roles that mean something

    A Data Steward approves ingests and runs resolutions. An Analyst reads, asks, and inspects lineage. No one edits the record by accident.

    ACORD as the backbone

    The canonical model is aligned to ACORD object and link types, so what you answer with is what your market already speaks.

    Quality kept in the open

    DQ findings ride along with the entities they touch — surfaced on the node, counted in every answer’s footer, never quietly dropped.

    Step into the graph.

    Pick a seat. The demo runs on a real claim, end to end — ingest, resolve, ask.

    Continue as Data Steward Approve ingests · run resolutions Continue as Analyst Read-only · ask & inspect lineage