Triple
T11798278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summerhill |
E280557
|
entity |
| Predicate | servedBy |
P82
|
FINISHED |
| Object | Yonge–University subway line |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yonge–University subway line Context triple: [Summerhill, servedBy, Yonge–University subway line]
-
A.
Line 1 Yonge–University
chosen
Line 1 Yonge–University is the busiest and oldest subway line in Toronto’s transit system, forming a U-shaped route through the city’s downtown core and major north–south corridors.
-
B.
Line 2 Bloor–Danforth
Line 2 Bloor–Danforth is a major east–west subway line in Toronto’s rapid transit system, running primarily along Bloor Street and Danforth Avenue.
-
C.
TTC Line 4 Sheppard
TTC Line 4 Sheppard is a short east–west subway line in Toronto’s rapid transit network, running under Sheppard Avenue East and connecting several North York neighborhoods to the broader TTC system.
-
D.
Richmond Hill line
The Richmond Hill line is a GO Transit commuter rail corridor in the Greater Toronto Area that runs between Toronto’s Union Station and communities to the north along the Don Valley and Richmond Hill.
-
E.
Yonge Street subway corridor
The Yonge Street subway corridor is a major rapid transit route in Toronto that follows Yonge Street and forms the backbone of the city’s subway network.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.