Triple
T37423095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roncesvalles streetcar routes |
E929914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toronto Transit Commission streetcar service |
C31011
|
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: Toronto Transit Commission streetcar service Context triple: [Roncesvalles streetcar routes, instanceOf, Toronto Transit Commission streetcar service]
-
A.
Toronto Transit Commission route
chosen
A Toronto Transit Commission route is a defined public transit service path, including its stops, schedule, and operating characteristics, used to transport passengers within the Greater Toronto Area.
-
B.
Toronto subway rolling stock
Toronto subway rolling stock comprises the various generations of electric multiple-unit trains used to provide rapid transit service on the Toronto Transit Commission’s subway and RT lines.
-
C.
Chicago Transit Authority service
Chicago Transit Authority service represents the public transportation operations, including bus and rail routes, schedules, and related customer services, provided by the CTA within the Chicago metropolitan area.
-
D.
heritage streetcar
A heritage streetcar is a restored or replica electric tram operated primarily for historical preservation, tourism, or nostalgic public transit experiences, often using vintage vehicles and traditional infrastructure.
-
E.
Yarra Trams service
A Yarra Trams service is an individual scheduled tram journey operated on Melbourne’s tram network, defined by its route, timetable, and vehicle providing passenger transport between designated stops.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.