Triple
T14504900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasserstraßen- und Schifffahrtsverwaltung des Bundes |
E340239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterways authority |
C19730
|
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: waterways authority Context triple: [Wasserstraßen- und Schifffahrtsverwaltung des Bundes, instanceOf, waterways authority]
-
A.
waterfront management agency
A waterfront management agency is an organization responsible for planning, regulating, and coordinating the sustainable use, development, and protection of coastal and shoreline areas.
-
B.
water management agency
chosen
A water management agency is an organization responsible for planning, regulating, and overseeing the sustainable allocation, use, and protection of water resources within a defined region.
-
C.
waterways charity
A waterways charity is an organization dedicated to protecting, restoring, and enhancing rivers, canals, and other inland waterways for environmental, recreational, and community benefit.
-
D.
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.
-
E.
flood control agency
A flood control agency is an organization responsible for planning, implementing, and managing measures to prevent, mitigate, and respond to flooding in a specific region.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:21 a.m.