Triple
T6617051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJmuiden locks |
E149578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | waterway infrastructure |
C14228
|
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 infrastructure Context triple: [IJmuiden locks, instanceOf, waterway infrastructure]
-
A.
canal infrastructure
Canal infrastructure encompasses the engineered systems, structures, and facilities—such as channels, locks, dams, embankments, and control mechanisms—designed to manage and support waterborne transport, irrigation, drainage, and water regulation along artificial waterways.
-
B.
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.
-
C.
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.
-
D.
lock and dam structure
chosen
A lock and dam structure is an engineered system on a waterway that combines a gated dam to control water levels with a lock chamber to raise and lower vessels between different elevations for safe and efficient navigation.
-
E.
flood control facility
A flood control facility is an engineered structure or system designed to manage, divert, store, or reduce excess water flow to prevent or mitigate flooding in surrounding areas.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:58 p.m.