Triple
T1385879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namami Gange |
E29843
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | river conservation programme |
C3134
|
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 programme Context triple: [Namami Gange, instanceOf, river conservation programme]
-
A.
water management project
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.
-
B.
water resources programme
chosen
A water resources programme is an organized set of policies, projects, and management activities aimed at sustainably developing, allocating, protecting, and monitoring water resources to meet environmental, social, and economic needs.
-
C.
watershed association
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.
-
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
A river is a natural flowing body of water, usually freshwater, that moves continuously along a defined channel from higher elevations toward lower ones, often emptying into a sea, lake, or another river.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.