Triple
T30852114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic |
E785808
|
entity |
| Predicate | openedAsMetroRailStation |
P60932
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Atlantic, openedAsMetroRailStation, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsMetroRailStation Context triple: [Atlantic, openedAsMetroRailStation, 2009]
-
A.
openedAsTransitStation
Indicates that an entity began operation specifically as a transit station at the time it was opened.
-
B.
openedAsMBTAStation
Indicates that an entity began operation specifically as an MBTA station at a particular time.
-
C.
openedAsSkyTrainStation
Indicates that an entity began operation specifically as a SkyTrain station at the time it was opened.
-
D.
openedAsMetrolinkStop
Indicates that a location began operation specifically as a Metrolink transit stop.
-
E.
openedAsUndergroundStation
chosen
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 8:46 p.m.