Triple
T10858983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashington railway station |
E256344
|
entity |
| Predicate | reopenedAsPassengerStation |
P73296
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [Ashington railway station, reopenedAsPassengerStation, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsPassengerStation Context triple: [Ashington railway station, reopenedAsPassengerStation, 2024]
-
A.
reopenedAsSubwayStation
Indicates that a previously closed or differently used station has been opened again specifically as a subway station.
-
B.
reopenedAsMetroStation
Indicates that a previously closed or differently used station was later reopened specifically as a metro station.
-
C.
reopenedRailwayStationYear
chosen
Indicates the year in which a previously closed railway station was reopened to service.
-
D.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
E.
reopenedAsHeritageStation
Indicates that a station, once closed or repurposed, has been reopened specifically as a heritage or historical railway station.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751500e248190823a16f2c85ad829 |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.