Triple
T9974869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bury Interchange |
E196300
|
entity |
| Predicate | openedAsBusStation |
P68211
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [Bury Interchange, openedAsBusStation, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsBusStation Context triple: [Bury Interchange, openedAsBusStation, 1970]
-
A.
openedAsBusTunnelStation
Indicates that a station was originally opened for service as part of a bus tunnel system rather than as a conventional rail or metro station.
-
B.
openedAsTransitStation
chosen
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
C.
openedAsTransportationCenter
Indicates that something was inaugurated or began operation specifically in the role of a transportation center.
-
D.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
-
E.
openedAsMetrolinkStop
Indicates that a location began operation specifically as a Metrolink transit stop.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb849da448190b826cb8fbf2eeb89 |
completed | April 2, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.