Triple

T33273911
Position Surface form Disambiguated ID Type / Status
Subject Imperfect Justice: Prosecuting Casey Anthony E851852 entity
Predicate mainProsecutorDescribed P1694 FINISHED
Object Jeff Ashton E2043238 NE 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: Jeff Ashton | Statement: [Imperfect Justice: Prosecuting Casey Anthony, mainProsecutorDescribed, Jeff Ashton]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainProsecutorDescribed
Context triple: [Imperfect Justice: Prosecuting Casey Anthony, mainProsecutorDescribed, Jeff Ashton]
  • A. mainPersecutor
    Indicates that one entity is the primary agent responsible for persecuting or oppressing another entity.
  • B. prosecutorSought
    Indicates that a prosecutor actively pursued or requested a particular legal action, charge, or outcome against a party.
  • C. notableProsecutor chosen
    Indicates that the person served as a prosecutor in a way that is widely recognized as significant or noteworthy.
  • D. subjectOfProsecution
    Indicates that an entity is the target or focus of a legal prosecution or criminal proceeding initiated by an authority.
  • E. subsequentProsecutor
    Indicates that one prosecutor follows or succeeds another in handling the same or a related legal case.
  • F. None of above.

Provenance (4 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_69f349653da08190819876015a298fdb completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f7516d5b4081908588a6feb541f355 completed May 3, 2026, 1:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a35431605108190888a582511ad752f completed June 19, 2026, 1:24 p.m.
PD Predicate disambiguation batch_69f74d40ebb081909daf60623e38f41d completed May 3, 2026, 1:27 p.m.
Created at: May 1, 2026, 1:32 a.m.