Triple

T775010
Position Surface form Disambiguated ID Type / Status
Subject The Triangle E16368 entity
Predicate hasCentralCity P3940 FINISHED
Object Durham E158 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: Durham | Statement: [The Triangle, hasCentralCity, Durham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Durham
Context triple: [The Triangle, hasCentralCity, Durham]
  • A. Durham
    Durham is a historic cathedral city in northeast England known for its Norman architecture and prestigious university.
  • B. Durham, North Carolina chosen
    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.
  • C. Norfolk
    Norfolk is a county in the East of England known for its rural landscapes, historic market towns, and extensive coastline along the North Sea.
  • D. 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.
  • E. York
    York is a historic former municipality in Ontario, Canada, that is now part of the modern city of Toronto.
  • 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_69a49369a0848190af883934cee3db4c completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a73236288190b82d66202f2f7399 completed March 1, 2026, 8:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac3b9557cc8190be3137aabdd36216 completed March 7, 2026, 2:52 p.m.
Created at: March 1, 2026, 7:37 p.m.