Triple
T28779239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internal Drainage Boards |
E726629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flood risk management authority |
C12171
|
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: flood risk management authority Context triple: [Internal Drainage Boards, instanceOf, flood risk management authority]
-
A.
flood control agency
chosen
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.
-
B.
flood risk reduction program
A flood risk reduction program is an organized set of policies, projects, and practices designed to lessen the likelihood and impacts of flooding on people, property, and the environment.
-
C.
waterway management organization
A waterway management organization is an entity responsible for planning, regulating, maintaining, and improving rivers, canals, and related water infrastructure to ensure safe navigation, environmental protection, and sustainable water use.
-
D.
flood hazard designation
A flood hazard designation is a classification assigned to geographic areas indicating their level of risk for flooding, typically used for planning, insurance, and regulatory purposes.
-
E.
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.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:18 a.m.