Triple
T20331516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvet Bridge |
E492493
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Durham city centre |
—
|
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 city centre | Statement: [Elvet Bridge, connects, Durham city centre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durham city centre Context triple: [Elvet Bridge, connects, Durham city centre]
-
A.
Newcastle city centre
Newcastle city centre is the main commercial, cultural, and retail hub of Newcastle upon Tyne in northeast England.
-
B.
Durham
Durham is a small rural community located in Pictou County in the Canadian province of Nova Scotia.
-
C.
Durham
chosen
Durham is a historic cathedral city in northeast England known for its Norman architecture and prestigious university.
-
D.
Durham
Durham is a regional municipality in Southern Ontario, Canada, encompassing several communities east of Toronto including cities like Whitby and Oshawa.
-
E.
Durham
Durham is a common English surname of Old English origin, associated with various notable individuals and places.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e7baf481909282293d78597634 |
completed | April 20, 2026, 7 p.m. |
Created at: April 16, 2026, 11:22 a.m.