Triple
T12653244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utrecht canal system |
E302217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | urban waterway system |
C6053
|
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 waterway system Context triple: [Utrecht canal system, instanceOf, urban waterway system]
-
A.
urban watercourse
An urban watercourse is a natural or engineered channel of flowing water that runs through a city or town, shaped and managed by surrounding urban infrastructure and land use.
-
B.
waterway network
chosen
A waterway network is an interconnected system of natural and artificial water channels (such as rivers, canals, and streams) designed or utilized for the movement, distribution, and management of water and waterborne transport.
-
C.
water infrastructure
Water infrastructure encompasses the systems, facilities, and networks designed to source, treat, store, distribute, and manage water and wastewater for human, industrial, and environmental needs.
-
D.
water supply system
A water supply system is an interconnected network of sources, treatment facilities, storage structures, and distribution pipelines designed to deliver safe and reliable water to end users.
-
E.
engineered waterway
An engineered waterway is a human-made or heavily modified channel or system designed to control, convey, or manage water for purposes such as navigation, irrigation, drainage, flood control, or power generation.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:18 p.m.