Triple
T13025136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT West End Line |
E326284
|
entity |
| Predicate | openedAsPassengerService |
P107520
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [BMT West End Line, openedAsPassengerService, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsPassengerService Context triple: [BMT West End Line, openedAsPassengerService, 1916]
-
A.
openedAsMBTAService
Indicates that a transit facility or line began operation specifically as part of the MBTA (Massachusetts Bay Transportation Authority) service.
-
B.
openedForShuttleService
Indicates that a location or facility has begun operating to provide shuttle transportation services.
-
C.
formerPassengerService
Indicates that an entity previously provided passenger transportation services but no longer does so.
-
D.
openedAsMetraService
Indicates that a transportation facility or line began operating specifically as part of the Metra commuter rail service.
-
E.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efac71881908a21d70c3c6ce099 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:53 p.m.