Triple
T33643722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradhan Mantri Krishi Sinchayee Yojana |
E861900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | irrigation 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: irrigation programme Context triple: [Pradhan Mantri Krishi Sinchayee Yojana, instanceOf, irrigation programme]
-
A.
irrigation organization
An irrigation organization is an entity that plans, manages, and coordinates the distribution and maintenance of water resources and infrastructure for agricultural or landscape irrigation within a defined area.
-
B.
irrigation network
An irrigation network is an interconnected system of channels, pipes, and control structures designed to distribute water efficiently from a source to agricultural fields or other areas requiring controlled watering.
-
C.
irrigated district
An irrigated district is a geographically defined area where water is systematically supplied and managed, typically through infrastructure like canals and pipelines, to support agricultural production and related land uses.
-
D.
irrigation command area
An irrigation command area is the total land surface that can be supplied with water from a specific irrigation system or source under its designed operating conditions.
-
E.
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.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.