Triple
T8237624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPRINTER light rail |
E192450
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diesel multiple-unit light rail service |
C21224
|
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: diesel multiple-unit light rail service Context triple: [SPRINTER light rail, instanceOf, diesel multiple-unit light rail service]
-
A.
diesel light rail line
chosen
A diesel light rail line is a passenger rail transit system that operates lighter, typically more frequent trains powered by diesel engines on dedicated or shared tracks, serving urban or regional corridors.
-
B.
light rail transit line
A light rail transit line is a fixed-route urban or suburban rail corridor using electrically powered, relatively low-capacity trains that operate on dedicated or semi-exclusive tracks to provide frequent, short- to medium-distance passenger service.
-
C.
light rail vehicle
A light rail vehicle is a rail-based transit vehicle designed for urban and suburban passenger service, typically operating on dedicated or shared tracks with frequent stops and moderate capacity.
-
D.
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.
-
E.
rapid transit line
A rapid transit line is a high-capacity, high-frequency urban rail route operating on an exclusive or mostly separated right-of-way to provide fast, reliable public transportation between key areas of a city or metropolitan region.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:47 p.m.