Triple
T8715010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich U-Bahn lines U3 and U6 |
E206871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rapid transit line group |
C24948
|
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: rapid transit line group Context triple: [Munich U-Bahn lines U3 and U6, instanceOf, rapid transit line group]
-
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 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.
-
C.
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.
-
D.
rapid transit division
A rapid transit division is an organizational unit within a transportation agency responsible for planning, operating, and maintaining high-frequency, high-capacity urban rail or bus rapid transit services.
-
E.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.