Triple

T37510739
Position Surface form Disambiguated ID Type / Status
Subject intake and records division E932208 entity
Predicate dataResponsibility P636 FINISHED
Object preserving integrity of court records LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: preserving integrity of court records | Statement: [intake and records division, dataResponsibility, preserving integrity of court records]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataResponsibility
Context triple: [intake and records division, dataResponsibility, preserving integrity of court records]
  • A. distributionResponsibility
    Indicates responsibility for managing, overseeing, or executing the distribution or delivery of something from one party to others.
  • B. responsibleFor chosen
    Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
  • C. securityResponsibilityModel
    Indicates the framework or scheme that defines how security responsibilities are allocated and managed among involved parties.
  • D. safetyResponsibilityOf
    Indicates that one entity holds responsibility for ensuring the safety of another entity or context.
  • E. dataOwner
    Indicates that one entity has ownership, control, or primary responsibility over a particular set of data associated with another entity.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69f76ec5268481909ea01c73aeeefd42 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba5eec0448190a5e6f0c43fdcd0e3 completed May 6, 2026, 8:34 p.m.
PD Predicate disambiguation batch_69fba34edd548190bfa980e6e16e0a88 completed May 6, 2026, 8:23 p.m.
Created at: May 3, 2026, 4:17 p.m.