Triple
T35395983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Cut |
E1023078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | canalised river channel |
C6500
|
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: canalised river channel Context triple: [New Cut, instanceOf, canalised river channel]
-
A.
stream corridor
A stream corridor is the linear landscape zone encompassing a stream and its adjacent floodplain, vegetation, and associated habitats that together influence the stream’s hydrology, ecology, and geomorphology.
-
B.
drainage channel
chosen
A drainage channel is a constructed or natural linear feature designed to collect and convey excess surface or subsurface water away from an area to prevent flooding, erosion, or waterlogging.
-
C.
river distributary
A river distributary is a branch of a river that diverges from the main channel and flows away from it, typically found in delta regions where sediment deposition causes the river to split into multiple smaller channels.
-
D.
constricted water channel
A constricted water channel is a narrow, often engineered or naturally formed passage that restricts and directs the flow of water, increasing velocity and influencing local hydrodynamics.
-
E.
river corridor
A river corridor is the linear landscape surrounding a river, including its channel, banks, floodplain, and adjacent habitats, through which water, sediment, organisms, and energy flow and interact.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.