Triple
T10146427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nashua River Watershed Association |
E231718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river conservation organization |
C974
|
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 conservation organization Context triple: [Nashua River Watershed Association, instanceOf, river conservation organization]
-
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 association
chosen
A watershed association is a community-based organization dedicated to protecting, restoring, and sustainably managing the land, water, and ecological resources within a specific watershed.
-
C.
river basin organization
A river basin organization is an institutional body responsible for coordinating the management, development, and protection of water and related resources within a defined river basin across sectors and jurisdictions.
-
D.
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.
-
E.
nature conservation organisation
A nature conservation organisation is an entity dedicated to protecting, restoring, and sustainably managing natural environments and biodiversity through research, advocacy, education, and on-the-ground conservation actions.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 9:07 p.m.