Triple
T10094478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungabhadra Left Bank Canal |
E215827
|
entity |
| Predicate | usesWaterFor |
P68556
|
FINISHED |
| Object | agricultural irrigation |
—
|
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: agricultural irrigation | Statement: [Tungabhadra Left Bank Canal, usesWaterFor, agricultural irrigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWaterFor Context triple: [Tungabhadra Left Bank Canal, usesWaterFor, agricultural irrigation]
-
A.
hasWaterUse
chosen
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
B.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
C.
waterRequirement
Indicates the amount or conditions of water needed for an entity to grow, function, or be maintained properly.
-
D.
usedIrrigation
Indicates that an entity applied or employed an irrigation system or method to supply water to land or crops.
-
E.
waterInput
Indicates that an entity receives or is supplied with water from another source or system.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd0784c288190967d143beca32c4b |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.