Triple
T30970316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA Line 12 |
E789076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commuter rail line internal designation |
C57368
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: commuter rail line internal designation Context triple: [MBTA Line 12, instanceOf, commuter rail line internal designation]
-
A.
public transit line designation
A public transit line designation is a unique identifier, such as a number, letter, color, or name, used to distinguish and communicate specific routes within a transportation network.
-
B.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
C.
MBTA internal line code
chosen
An MBTA internal line code is a standardized identifier used within the Massachusetts Bay Transportation Authority’s systems to uniquely reference and manage specific transit lines across operations, scheduling, and data reporting.
-
D.
regional rail service brand
A regional rail service brand is a distinct identity used to market and organize passenger train services within a specific geographic area, encompassing naming, visual design, and service characteristics.
-
E.
rapid transit line segment
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
- F. None of above.
Provenance (1 batch)
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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.