Triple
T18680227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prebends Bridge |
E456712
|
entity |
| Predicate | near |
P350
|
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: [Prebends Bridge, near, Durham city centre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durham city centre Context triple: [Prebends Bridge, near, 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
chosen
Durham is a historic cathedral city in northeast England known for its Norman architecture and prestigious university.
-
C.
Durham
Durham is a regional municipality in Southern Ontario, Canada, encompassing several communities east of Toronto including cities like Whitby and Oshawa.
-
D.
Durham
Durham is a common English surname of Old English origin, associated with various notable individuals and places.
-
E.
Morpeth
Morpeth is a historic market town in Northumberland, England, known for its traditional architecture and role as a local commercial and administrative centre.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2783648190bb602e2b07eedf92 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 10, 2026, 11:48 a.m.