Triple

T8744085
Position Surface form Disambiguated ID Type / Status
Subject Jed York E207779 entity
Predicate familyName P18 FINISHED
Object York unclear NED1 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: York | Statement: [Jed York, familyName, York]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: York
Context triple: [Jed York, familyName, York]
  • A. York
    York is a historic walled city in North Yorkshire, England, renowned for its medieval architecture, including York Minster, and its rich Roman and Viking heritage.
  • B. York
    York is a historic former municipality in Ontario, Canada, that is now part of the modern city of Toronto.
  • C. York
    York was an enslaved African American man who played a crucial yet long-overlooked role as a full participant in the Lewis and Clark Expedition across the American West.
  • D. York
    York is a well-known global brand of heating, ventilation, air conditioning, and refrigeration (HVAC&R) equipment owned by Johnson Controls.
  • E. Manchester
    Manchester is a suburban town in central Connecticut known for its historic mills, shopping districts, and residential communities within the Greater Hartford area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69ca835bb2bc819084bb5906cb6ef7f8 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5d72e47c819099540d062d35ebd5 completed March 31, 2026, 11:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf518750948190a42ad8fc352ac851 completed April 3, 2026, 5:35 a.m.
Created at: March 30, 2026, 6:38 p.m.