Triple
T28596750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium Line at Production Way–University station |
E723795
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SkyTrain service pattern |
C20256
|
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: SkyTrain service pattern Context triple: [Millennium Line at Production Way–University station, instanceOf, SkyTrain service pattern]
-
A.
rapid transit network
A rapid transit network is an integrated system of high-capacity, high-frequency urban rail or bus lines designed to move large numbers of passengers quickly and efficiently across a metropolitan area.
-
B.
railway line service pattern
chosen
A railway line service pattern defines the structured arrangement of train services over a route, including stopping sequences, frequencies, and service types that determine how trains operate along the line.
-
C.
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.
-
D.
rapid transit line segment
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
-
E.
rapid transit line group
A rapid transit line group is a collection of closely related or jointly operated rapid transit lines that share infrastructure, service patterns, or branding within a transit network.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:22 a.m.