Triple
T7337498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trieste city bus network |
E169165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bus transport system |
C911
|
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 transport system Context triple: [Trieste city bus network, instanceOf, bus transport system]
-
A.
public transit system
chosen
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
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.
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.
rubber-tired transit system
A rubber-tired transit system is a guided public transportation mode in which vehicles run on rubber tires along a dedicated roadway or track, often combining bus-like flexibility with rail-like guidance and capacity.
-
E.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:04 p.m.