Triple
T857348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutlej River |
E18520
|
entity |
| Predicate | waterAllocatedTo |
P20226
|
FINISHED |
| Object | India under Indus Waters Treaty |
—
|
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: India under Indus Waters Treaty | Statement: [Sutlej River, waterAllocatedTo, India under Indus Waters Treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterAllocatedTo Context triple: [Sutlej River, waterAllocatedTo, India under Indus Waters Treaty]
-
A.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
B.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
C.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
D.
waterManagementAuthority
Indicates that an entity has official responsibility for overseeing, regulating, or managing water resources, services, or infrastructure for a given area or system.
-
E.
waterRequirement
Indicates the amount or conditions of water needed for an entity to grow, function, or be maintained properly.
- F. None of above. chosen
Provenance (4 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac4d47508190b48d944aa2d881bf |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.