Triple
T8213222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames Estuary 2100 flood management plan |
E191871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flood risk management plan |
C1458
|
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 plan Context triple: [Thames Estuary 2100 flood management plan, instanceOf, flood risk management plan]
-
A.
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.
-
B.
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.
-
C.
water management project
chosen
A water management project is an organized initiative that plans, develops, and operates systems and practices to sustainably collect, store, distribute, and protect water resources for human and environmental needs.
-
D.
geohazards risk reduction program
A geohazards risk reduction program is a coordinated set of policies, practices, and interventions designed to identify, assess, and mitigate risks from geological hazards such as earthquakes, landslides, and volcanic eruptions to protect people, infrastructure, and the environment.
-
E.
ecosystem management plan
An ecosystem management plan is a strategic, science-based framework that outlines goals, actions, and monitoring methods to maintain or restore the health, resilience, and sustainability of a specific ecosystem while balancing ecological, social, and economic needs.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:44 p.m.