Triple
T17502656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadowhall Interchange |
E426228
|
entity |
| Predicate | openedForRail |
P16837
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Meadowhall Interchange, openedForRail, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForRail Context triple: [Meadowhall Interchange, openedForRail, 1990]
-
A.
openedToRailTraffic
chosen
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
B.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
-
C.
openedAsRailroad
Indicates that a transportation line or route was originally inaugurated and operated as a railroad.
-
D.
openedAsRailTerminal
Indicates that a facility or location began operation specifically as a rail terminal when it first opened.
-
E.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45212ea608190a3f225ba736cd754 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.