Triple

T22058996
Position Surface form Disambiguated ID Type / Status
Subject Robert Yates E545101 entity
Predicate familyName P18 FINISHED
Object Yates NE NERFINISHED

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: Yates | Statement: [Robert Yates, familyName, Yates]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yates
Context triple: [Robert Yates, familyName, Yates]
  • A. Yates chosen
    Yates is a surname of English origin borne by various notable individuals across literature, politics, sports, and other fields.
  • B. Challis
    Challis is an English surname borne by various notable individuals across fields such as cinematography, science, and public service.
  • C. Shadbolt
    Shadbolt is a surname most notably associated with Sir Nigel Shadbolt, a prominent British computer scientist and artificial intelligence researcher.
  • D. Heseltine
    Heseltine is a surname most prominently associated with Michael Heseltine, a senior British Conservative politician and former Deputy Prime Minister.
  • E. Collycroft
    Collycroft is a residential area and suburb within the town of Bedworth in Warwickshire, England.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e3377c48190890c17407b9527d6 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1285ac9608190ab4f89d4ee7350d0 completed April 28, 2026, 9:36 p.m.
Created at: April 16, 2026, 8:27 p.m.