Triple

T25881423
Position Surface form Disambiguated ID Type / Status
Subject John G. Heyburn II E652058 entity
Predicate dateOfRetirementFromActiveService P7188 FINISHED
Object 2014-04-01 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: 2014-04-01 | Statement: [John G. Heyburn II, dateOfRetirementFromActiveService, 2014-04-01]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dateOfRetirementFromActiveService
Context triple: [John G. Heyburn II, dateOfRetirementFromActiveService, 2014-04-01]
  • A. retirementDate chosen
    Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
  • B. retiredFrom
    Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
  • C. retiredFromFrontlineService
    Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
  • D. retiredFromUSMilitary
    Indicates that an individual previously served in the United States military and has formally ended their military career or service.
  • E. hasMilitaryServiceEnd
    Indicates the date or point in time at which an entity’s period of military service concludes.
  • 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_69e7ab3b92cc81908febd90317862647 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6352fdb788190b9bad30243690743 completed May 2, 2026, 5:32 p.m.
PD Predicate disambiguation batch_69f63182f1408190bddc1214fcbd6145 completed May 2, 2026, 5:16 p.m.
Created at: April 22, 2026, 8:16 a.m.