Triple
T4178945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA diesel locomotives |
E86545
|
entity |
| Predicate | introducedForMBTA |
P3018
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [MBTA diesel locomotives, introducedForMBTA, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForMBTA Context triple: [MBTA diesel locomotives, introducedForMBTA, 1970s]
-
A.
introducedByAmtrak
Indicates that something (such as a service, policy, feature, or change) was initiated, launched, or brought into use by Amtrak.
-
B.
introducedFor
chosen
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
C.
hasFareControlIntegrationSince
Indicates that a fare control system has been integrated with another system or entity starting from a specific point in time.
-
D.
commuterRailMode
Indicates that the relationship involves travel or transportation specifically by commuter rail as the mode of transit between the related entities.
-
E.
openedAsMBTAStation
Indicates that an entity began operation specifically as an MBTA station at a particular time.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.