Triple
T6913213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heritage Corridor |
E159985
|
entity |
| Predicate | openedAsMetraService |
P74107
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Heritage Corridor, openedAsMetraService, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsMetraService Context triple: [Heritage Corridor, openedAsMetraService, 1980s]
-
A.
openedAsMetroNorthService
Indicates that a transportation facility or line began operation specifically as part of the Metro-North Railroad service.
-
B.
openedAsMetrolinkStop
Indicates that a location began operation specifically as a Metrolink transit stop.
-
C.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
-
D.
openedAsMBTAStation
Indicates that an entity began operation specifically as an MBTA station at a particular time.
-
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. 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9dbca6c819091d8b65e54ada5d9 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:25 p.m.