Triple
T22810226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ’s-Hertogenbosch–Maas |
E564651
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterway reach |
C40473
|
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: waterway reach Context triple: [’s-Hertogenbosch–Maas, instanceOf, waterway reach]
-
A.
navigable waterway
A navigable waterway is a natural or artificial body of water, such as a river, canal, or channel, that is deep and wide enough for vessels to travel safely for transportation or commerce.
-
B.
waterway section
chosen
A waterway section is a defined segment of a natural or artificial watercourse, such as a river, canal, or channel, characterized by specific geographic, hydraulic, or administrative properties.
-
C.
waterway network
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.
-
D.
waterway feature
A waterway feature is any natural or man-made linear or areal element that involves the presence, movement, or containment of water, such as rivers, canals, streams, or channels.
-
E.
regulated river reach
A regulated river reach is a segment of a river whose flow, water level, or timing is intentionally controlled by human-made structures such as dams, weirs, or diversion works.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:32 p.m.