Triple
T1814005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County Durham |
E40394
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Durham |
E59757
|
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: [County Durham, contains, Durham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durham Context triple: [County Durham, contains, Durham]
-
A.
Durham
chosen
Durham is a historic cathedral city in northeast England known for its Norman architecture and prestigious university.
-
B.
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.
-
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_69a88643a3388190a612f2ebe1fb29e7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa65c905ec8190bea7cd72d218487a |
completed | March 6, 2026, 5:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adfb9f3354819097ce858a8706c324 |
completed | March 8, 2026, 10:43 p.m. |
Created at: March 4, 2026, 7:32 p.m.