Triple

T21890633
Position Surface form Disambiguated ID Type / Status
Subject David Huddleston E540532 entity
Predicate familyName P18 FINISHED
Object Huddleston 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: Huddleston | Statement: [David Huddleston, familyName, Huddleston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Huddleston
Context triple: [David Huddleston, familyName, Huddleston]
  • A. Huddleston chosen
    Huddleston is an English-origin surname borne by various notable individuals, including figures in politics, religion, and the arts.
  • B. Hunston
    Hunston is a small village and civil parish on the Manhood Peninsula in West Sussex, England.
  • C. Hooton
    Hooton is a village and residential area on the Wirral Peninsula in Cheshire, England, known for its transport links and proximity to major road and rail routes.
  • D. Halliford
    Halliford is a locality in Surrey, England, known as part of the Shepperton and Upper Halliford suburban area within the London commuter belt.
  • E. Hosbrook
    Hosbrook is a family surname, likely of English origin, shared by individuals such as Brenda Hosbrook.
  • 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_69e0c47a95908190ae3e19b716accb3d completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f11fc2124c8190a79cf115a1d30283 completed April 28, 2026, 8:59 p.m.
Created at: April 16, 2026, 7:06 p.m.