Triple
T13530896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nijmegen cycling infrastructure |
E323128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban cycling infrastructure network |
C4130
|
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: urban cycling infrastructure network Context triple: [Nijmegen cycling infrastructure, instanceOf, urban cycling infrastructure network]
-
A.
national cycling infrastructure
National cycling infrastructure is the integrated network of bike paths, lanes, facilities, and supporting policies designed at a country-wide level to enable safe, efficient, and accessible cycling for transportation and recreation.
-
B.
cycle network
A cycle network is a graph structure in which nodes are connected in a closed loop so that each node is part of at least one simple cycle, enabling circular paths for flow, communication, or dependencies.
-
C.
transport infrastructure network
chosen
A transport infrastructure network is an interconnected system of physical routes and facilities—such as roads, railways, ports, and airports—designed to enable the efficient movement of people and goods across regions.
-
D.
pedestrian network
A pedestrian network is an interconnected system of walkways, sidewalks, crossings, and paths designed to facilitate safe and efficient movement of people on foot within and between areas.
-
E.
city network
A city network is an interconnected system of urban areas linked by transportation, communication, and economic relationships that facilitate the flow of people, goods, information, and services.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.