Triple
T24157096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotswood Bridge |
E598713
|
entity |
| Predicate | isNorthEndIn |
P15231
|
FINISHED |
| Object | Scotswood, Newcastle upon Tyne |
—
|
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: Scotswood, Newcastle upon Tyne | Statement: [Scotswood Bridge, isNorthEndIn, Scotswood, Newcastle upon Tyne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNorthEndIn Context triple: [Scotswood Bridge, isNorthEndIn, Scotswood, Newcastle upon Tyne]
-
A.
locatedAtNorthernEndOf
chosen
Indicates that one entity is situated at or near the northernmost part or extremity of another entity.
-
B.
isEasternEndOf
Indicates that one entity forms or marks the easternmost end or boundary of another entity.
-
C.
isHomeEndFor
Indicates that something serves as the final destination, endpoint, or concluding location for a journey, process, or sequence.
-
D.
terminusNorth
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
E.
isNorthernmost
Indicates that one entity is located farther north than all other comparable entities in a given set or region.
- F. None of above.
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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e5bdb48190aa2d369942b85220 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:31 p.m.