Triple
T13741058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport for Wales integrated transport network |
E330084
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated public transport network |
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: integrated public transport network Context triple: [Transport for Wales integrated transport network, instanceOf, integrated public transport network]
-
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.
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.
-
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.
bus service network
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.
-
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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.