Triple
T10741088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Park Tunnel |
E253327
|
entity |
| Predicate | reopenedForRegularPassengerServices |
P77038
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Phoenix Park Tunnel, reopenedForRegularPassengerServices, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedForRegularPassengerServices Context triple: [Phoenix Park Tunnel, reopenedForRegularPassengerServices, 2016]
-
A.
reopenedAsMBTAService
Indicates that a previously closed service or line was reopened specifically as part of the MBTA (Massachusetts Bay Transportation Authority) system.
-
B.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
C.
closedForPassengers
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
D.
reopenedToTraffic
Indicates that a previously closed route or transportation facility has been opened again for use by traffic.
-
E.
openedToPassengerTraffic
chosen
Indicates that a transportation facility or route began operating and accepting passengers for regular use.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7104446288190800253f8b652f710 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.