Triple

T29186982
Position Surface form Disambiguated ID Type / Status
Subject Yamuna Action Plan projects E739894 entity
Predicate instanceOf P0 FINISHED
Object river pollution control programme C2343 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 pollution control programme
Context triple: [Yamuna Action Plan projects, instanceOf, river pollution control programme]
  • A. water pollution control program chosen
    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.
  • B. water pollution control law
    Water pollution control law is a body of legal rules and regulations designed to prevent, reduce, and remediate contamination of water resources by setting standards, permitting discharges, and enforcing compliance to protect human health and the environment.
  • C. river protection program
    A river protection program is an organized initiative that plans, implements, and monitors actions to preserve and restore the ecological health, water quality, and sustainable use of river systems.
  • D. water resources programme
    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.
  • E. 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.
  • 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_69f07cb74c2c8190ad396487fcb4fde6 completed April 28, 2026, 9:24 a.m.
Created at: April 28, 2026, noon