Triple

T20884334
Position Surface form Disambiguated ID Type / Status
Subject William of Durham E514234 entity
Predicate placeOfActivity P1527 FINISHED
Object Durham 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: Durham | Statement: [William of Durham, placeOfActivity, Durham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Durham
Context triple: [William of Durham, placeOfActivity, Durham]
  • A. Durham chosen
    Durham is a historic cathedral city in northeast England known for its Norman architecture and prestigious university.
  • B. Durham
    Durham is a regional municipality in Southern Ontario, Canada, encompassing several communities east of Toronto including cities like Whitby and Oshawa.
  • C. Durham
    Durham is a common English surname of Old English origin, associated with various notable individuals and places.
  • D. Durham
    Durham is a small rural community located in Pictou County in the Canadian province of Nova Scotia.
  • E. Durham, North Carolina
    Durham, North Carolina is a major city in the Research Triangle region known for Duke University, a strong research and tech economy, and a rich civil rights and tobacco-industry history.
  • 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_69e0b4f733f081908a401c0b7beb0b9f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c67bd32c819097301e330e358c49 completed April 21, 2026, 12:36 a.m.
Created at: April 16, 2026, 12:46 p.m.