Triple
T16325697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wearmouth Bridge |
E396410
|
entity |
| Predicate | formerToll |
P122723
|
FINISHED |
| Object | yes (historically on earlier bridge) |
—
|
LITERAL 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: yes (historically on earlier bridge) | Statement: [Wearmouth Bridge, formerToll, yes (historically on earlier bridge)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerToll Context triple: [Wearmouth Bridge, formerToll, yes (historically on earlier bridge)]
-
A.
formerTollRoad
Indicates that a road previously operated as a toll road but is no longer tolled.
-
B.
formerTransport
Indicates that an entity previously served as a means of transportation for another entity but no longer does so.
-
C.
tollIntroduced
Indicates that a toll was established or put into effect for using a particular route, facility, or service.
-
D.
fareSystemPreviously
Indicates that a particular fare system existed or was in use at an earlier time relative to another fare system or time period.
-
E.
formerLine
Indicates that an entity previously served as a particular transit or service line but no longer does so.
- F. None of above. chosen
Provenance (4 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b9dcb88190beb0ca2206729175 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.