Triple
T13233699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Line BRT stations (selected) |
E315085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bus rapid transit station group |
C32691
|
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: bus rapid transit station group Context triple: [Silver Line BRT stations (selected), instanceOf, bus rapid transit station group]
-
A.
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.
-
B.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
-
C.
group of rapid transit lines
A group of rapid transit lines is a collection of interconnected high-capacity urban rail or metro routes that operate together as a coordinated network to provide frequent, efficient public transportation.
-
D.
bus rapid transit line
A bus rapid transit line is a high-capacity bus corridor that uses dedicated lanes, priority signaling, and streamlined stations to provide fast, reliable, rail-like transit service.
-
E.
group of metro interchange stations
A group of metro interchange stations is a collection of transit hubs where multiple metro lines intersect, enabling passengers to transfer between routes within an urban rail network.
- F. None of above. chosen
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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:22 p.m.