Triple
T26104401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Scenic Rivers program |
E658496
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river protection program |
C51120
|
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: river protection program Context triple: [Ohio Scenic Rivers program, instanceOf, river protection program]
-
A.
river conservancy
River conservancy is the management and protection of river ecosystems through planning, regulation, restoration, and sustainable use to maintain their ecological health and benefits to society.
-
B.
watershed preserve
A watershed preserve is a protected natural area managed to safeguard the land, water, and ecological processes that collect, store, and filter water within a drainage basin.
-
C.
riverine sanctuary
A riverine sanctuary is a protected natural area centered around a river and its surrounding ecosystems, preserving aquatic and riparian habitats while supporting biodiversity and sustainable human use.
-
D.
water pollution control program
A water pollution control program is an organized set of policies, regulations, monitoring activities, and treatment measures designed to prevent, reduce, and manage contaminants entering water bodies to protect human health and aquatic ecosystems.
-
E.
river basin management plan
A river basin management plan is a strategic framework that outlines coordinated actions, policies, and measures to sustainably manage water resources, ecosystems, land use, and human activities within a defined river basin.
- F. None of above. chosen
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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:57 p.m.