Triple
T24618717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DC Streetcar |
E609343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | light rail–style transit system |
C2237
|
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: light rail–style transit system Context triple: [DC Streetcar, instanceOf, light rail–style transit system]
-
A.
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.
-
B.
light rail vehicle
chosen
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.
-
C.
rubber-tired transit system
A rubber-tired transit system is a guided public transportation mode in which vehicles run on rubber tires along a dedicated roadway or track, often combining bus-like flexibility with rail-like guidance and capacity.
-
D.
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.
-
E.
rapid transit vehicle
A rapid transit vehicle is a high-capacity, electrically powered rail car or train designed to provide frequent, fast, and reliable urban or suburban passenger transportation on dedicated or grade-separated tracks.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:32 a.m.