Triple
T8560103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Yamuna Canal |
E202668
|
entity |
| Predicate | waterAllocation |
P77607
|
FINISHED |
| Object | Haryana share of Yamuna waters |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Haryana share of Yamuna waters | Statement: [Western Yamuna Canal, waterAllocation, Haryana share of Yamuna waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterAllocation Context triple: [Western Yamuna Canal, waterAllocation, Haryana share of Yamuna waters]
-
A.
waterAllocatedTo
Indicates that a specified amount or portion of water has been designated or assigned for use by a particular entity, location, or purpose.
-
B.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
C.
waterManagementAuthority
Indicates that an entity has official responsibility for overseeing, regulating, or managing water resources, services, or infrastructure for a given area or system.
-
D.
waterSupplyShare
chosen
Indicates the proportion of a total water supply that is allocated to or used by a particular entity.
-
E.
waterRight
Indicates a legal or recognized entitlement that one party has to use or access water from a particular source under specified conditions.
- F. None of above.
Provenance (3 batches)
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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe949974c8190a75d9c767ca5fa5a |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.