Triple
T8114925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DART streetcar |
E189448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban rail transit service |
C912
|
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: urban rail transit service Context triple: [DART streetcar, instanceOf, urban rail transit service]
-
A.
rail transit
chosen
Rail transit is a public transportation system that moves passengers or freight along fixed steel tracks using trains, subways, trams, or light rail vehicles, typically in urban or intercity corridors.
-
B.
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.
-
C.
public transit system
A public transit system is an organized network of shared transportation services—such as buses, trains, subways, and trams—designed to move large numbers of people efficiently within and between urban and regional areas.
-
D.
suburban commuter train
A suburban commuter train is a passenger rail service designed to transport people efficiently between residential suburbs and urban centers, typically operating on fixed schedules with frequent stops during peak travel times.
-
E.
urban rail loop line
An urban rail loop line is a circular or near-circular transit route within a city that connects multiple districts and intersecting lines, allowing continuous, bidirectional travel without a terminal endpoint.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:33 p.m.