Triple
T34254233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flood Control Act of 1974 |
E878825
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flood control statute |
C18291
|
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 control statute Context triple: [Flood Control Act of 1974, instanceOf, flood control statute]
-
A.
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.
-
B.
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.
-
C.
levee system
A levee system is an integrated network of embankments, floodwalls, and related structures designed to contain or redirect water to protect land and infrastructure from flooding.
-
D.
water resources development act
chosen
The Water Resources Development Act is a recurring United States federal law that authorizes and guides the planning, construction, and maintenance of water resources projects such as navigation, flood control, and ecosystem restoration, primarily carried out by the U.S. Army Corps of Engineers.
-
E.
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.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.