Triple
T6866705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cullercoats Metro station |
E158418
|
entity |
| Predicate | reopenedAsMetroStation |
P74198
|
FINISHED |
| Object | 1980 |
—
|
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: 1980 | Statement: [Cullercoats Metro station, reopenedAsMetroStation, 1980]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedAsMetroStation Context triple: [Cullercoats Metro station, reopenedAsMetroStation, 1980]
-
A.
reopenedAsSubwayStation
Indicates that a previously closed or differently used station has been opened again specifically as a subway station.
-
B.
openedAsNYCSubwayStation
Indicates that an entity began operation specifically as a New York City Subway station at the time it opened.
-
C.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
D.
openedAsUndergroundStation
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
-
E.
openedAsMetrolinkStop
Indicates that a location began operation specifically as a Metrolink transit stop.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6da3b5510819093c5893ea92ac025 |
completed | March 27, 2026, 7:27 p.m. |
Created at: March 27, 2026, 2:21 p.m.