Triple
T31549523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto streetcar route 506 Carlton |
E804958
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toronto streetcar line |
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 streetcar line Context triple: [Toronto streetcar route 506 Carlton, instanceOf, Toronto streetcar line]
-
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.
Ontario Line station
An Ontario Line station is a transit facility along Toronto’s planned Ontario Line rapid transit route that provides passenger access, boarding, transfers, and related services for subway operations.
-
C.
DC Circulator line
A DC Circulator line is a specific bus route within Washington, D.C.’s Circulator transit system that provides frequent, low-cost service along a defined corridor connecting key neighborhoods and destinations.
-
D.
Chicago Transit Authority bus route
A Chicago Transit Authority bus route is a designated public transportation line that operates scheduled bus services along a specific path within the Chicago metropolitan area, connecting various neighborhoods, landmarks, and transit hubs.
-
E.
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.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:10 p.m.