Triple

T10147618
Position Surface form Disambiguated ID Type / Status
Subject Henry Vincent Yorke E231743 entity
Predicate familyName P18 FINISHED
Object Yorke E231743 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: Yorke | Statement: [Henry Vincent Yorke, familyName, Yorke]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yorke
Context triple: [Henry Vincent Yorke, familyName, Yorke]
  • A. Yorke chosen
    Yorke is an English surname historically associated with prominent figures in law, politics, and public life in Britain.
  • B. Peter Yorke
    Peter Yorke is a notable individual who shares the surname Yorke, recognized enough to be specifically cited as a bearer of the name.
  • C. Joseph Sydney Yorke
    Joseph Sydney Yorke was a British Royal Navy officer and politician of the late 18th and early 19th centuries, known for his service during the French Revolutionary and Napoleonic Wars.
  • D. Blurton
    Blurton is a suburban area in Stoke-on-Trent, Staffordshire, England, known primarily as a residential community.
  • E. Gilmour
    Gilmour is a surname most prominently associated with Canadian former professional ice hockey player Doug Gilmour.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca848364f881908a24366a6feec1db completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec011c24819089b456fc8b9ed80c completed April 2, 2026, 4:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d32ab35a508190a8eb1977e19ab8c5 completed April 6, 2026, 3:38 a.m.
Created at: March 30, 2026, 9:07 p.m.