Triple
T11586370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | METRO bus rapid transit |
E274765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-frequency transit service |
C8119
|
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: high-frequency transit service Context triple: [METRO bus rapid transit, instanceOf, high-frequency transit service]
-
A.
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.
-
B.
rapid rail system
A rapid rail system is a high-speed, high-capacity railway network designed to transport large numbers of passengers quickly and efficiently between urban or regional destinations using dedicated tracks and frequent service.
-
C.
rush-hour service
Rush-hour service is a transportation or customer service schedule that provides increased capacity or frequency during peak demand periods to accommodate higher user volumes efficiently.
-
D.
bus rapid transit line
chosen
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.
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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:38 p.m.