Triple
T34824301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadsbuitengracht |
E1003873
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defensive waterway |
C40354
|
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: defensive waterway Context triple: [Stadsbuitengracht, instanceOf, defensive waterway]
-
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.
coastal defence
Coastal defence is the set of structures, natural features, and management strategies designed to protect coastlines from erosion, flooding, and storm impacts.
-
C.
waterway feature
chosen
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.
-
D.
water barrier
A water barrier is a structure, material, or system designed to prevent or control the passage, infiltration, or flow of water between distinct areas or environments.
-
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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 4 p.m.