Triple
T19711645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R2 |
E473361
|
entity |
| Predicate | associatedStationCodeSystem |
P57418
|
FINISHED |
| Object | MBTA Red Line station codes |
—
|
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: MBTA Red Line station codes | Statement: [R2, associatedStationCodeSystem, MBTA Red Line station codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStationCodeSystem Context triple: [R2, associatedStationCodeSystem, MBTA Red Line station codes]
-
A.
hasStationCodeSystem
chosen
Indicates that an entity uses or is associated with a particular system for assigning or managing station codes.
-
B.
associatedStationQualifier
Indicates that a station is linked to another station with a specific qualifying role or context (such as type, function, or relationship).
-
C.
associatedStation
Indicates a relationship where one entity is linked or connected to a particular station as its relevant or related station.
-
D.
hasStationCode
Indicates that an entity is associated with a specific station identification code.
-
E.
associatedStationCategory
Indicates that one entity is linked to, or classified under, a particular category of station.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64408bde08190aa3bef8516491e03 |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.