Triple
T30298526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munich bus network |
E770587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of public transport |
C2489
|
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: component of public transport Context triple: [Munich bus network, instanceOf, component of public transport]
-
A.
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.
-
B.
public transportation infrastructure
chosen
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
C.
public transport technology
Public transport technology encompasses the systems, vehicles, infrastructure, and digital tools used to plan, operate, and optimize shared transportation services such as buses, trains, trams, and metros.
-
D.
public transportation partnership
A public transportation partnership is a collaborative arrangement between government agencies, private companies, and/or community organizations to plan, fund, operate, or improve shared transit services for the public.
-
E.
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.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:48 p.m.