Triple
T18908520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hradec Králové urban bus network |
E462532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bus-based public transit network |
C31035
|
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-based public transit network Context triple: [Hradec Králové urban bus network, instanceOf, bus-based public transit network]
-
A.
bus service network
chosen
A bus service network is an interconnected system of bus routes, stops, schedules, and vehicles designed to transport passengers efficiently across a defined geographic area.
-
B.
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.
-
C.
public transportation infrastructure
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.
-
D.
rapid transit network
A rapid transit network is an integrated system of high-capacity, high-frequency urban rail or bus lines designed to move large numbers of passengers quickly and efficiently across a metropolitan area.
-
E.
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.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:58 a.m.