Triple
T369646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 2 Bloor–Danforth |
E8239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toronto subway line |
C641
|
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 subway line Context triple: [Line 2 Bloor–Danforth, instanceOf, Toronto subway line]
-
A.
subway line
chosen
A subway line is a fixed route within an urban rail transit system, consisting of a sequence of stations and tracks over which trains operate according to a scheduled service.
-
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.
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.
-
D.
streetcar system
A streetcar system is an urban public transit network that operates rail vehicles on fixed tracks, typically embedded in city streets, to transport passengers along defined routes.
-
E.
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.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.