Trace the decision through relationships

Connect the claim document to its claimant and policy to recover the context of the escalation.

Question for this chapter

Can the next reviewer recover the complete claim context from one decision-log row?

Why this matters now

decision_log says what was decided and why automation stopped. Who filed the claim and which policy covers it live elsewhere. Seeing those relationships together shortens the path back to source context.

Try it

Open ontology_materialization and select Run. When it completes, run this query in Graph explorer:

MATCH (c:da_claimant)<-[:da_filed_by]-(d:da_document)-[:da_covered_by]->(p:da_policy)
WHERE d.claim_id = 'CLM-2025-006'
RETURN c, d, p
LIMIT 25

Success looks like this

The graph connects document CLM-2025-006 between Frank Wilson and POL-60444.

flowchart LR
    accTitle: Relationships for the escalated claim
    accDescr: Frank Wilson filed document CLM-2025-006, the document is covered by policy POL-60444, and the decision log records why a person must review it.
    claimant["Claimant<br/>Frank Wilson"] -->|"da_filed_by"| document["Claim document<br/>CLM-2025-006"]
    document -->|"da_covered_by"| policy["Policy<br/>POL-60444"]
    document -. "reason" .-> decision["Human review<br/>confidence 0.52"]

This result reconnects claim_documents, decision_log, and policy information by one claim ID.

Interpret the result

A handoff needs more than the decision. Decision, reason, source location, claimant, and policy context allow the next reviewer to reconstruct the same evidence.

All ten claimants and all ten policies appear only once in this sample. It cannot demonstrate a cluster of repeated claims. Focus here on connecting the context of one document accurately.

Deep dive — current scope of the human handoff

Every adjuster_id in decision_log is empty. The default Portal run also does not download the source PDF from object storage. The synthetic source is bundled at docai/data/pdf/clm_006.pdf.

This scenario creates the decision and reason for human review. Source viewing, reviewer assignment, final approval UI, and completed-review status require a separate operational workflow.

Next decision

You can now trace one claim. Next, widen the view to all ten samples and see how the operations team finds the same conclusion in the dashboard.