Triple
T14967136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Seattle Transit Tunnel |
E373218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bus rapid transit facility |
C35335
|
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 facility Context triple: [Downtown Seattle Transit Tunnel, instanceOf, bus rapid transit facility]
-
A.
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.
-
B.
rapid transit depot
A rapid transit depot is a specialized facility where urban rail vehicles are stored, inspected, maintained, and dispatched for service on a rapid transit network.
-
C.
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.
-
D.
bus rapid transit station group
A bus rapid transit station group is a coordinated set of closely spaced BRT stations or platforms that function together as a single operational unit to serve high-capacity, high-frequency bus services along a corridor.
-
E.
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.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:47 a.m.