Triple
T15485839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohri Canal |
E377044
|
entity |
| Predicate | distributesWaterTo |
P14199
|
FINISHED |
| Object | agricultural land |
—
|
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 land | Statement: [Rohri Canal, distributesWaterTo, agricultural land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributesWaterTo Context triple: [Rohri Canal, distributesWaterTo, agricultural land]
-
A.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
B.
waterDistributionMethod
Indicates how water is delivered, supplied, or allocated from a source to its intended recipients or locations.
-
C.
waterAllocatedTo
Indicates that a specified amount or portion of water has been designated or assigned for use by a particular entity, location, or purpose.
-
D.
transportsWaterTo
chosen
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
E.
receivesMoistureFrom
Indicates that one entity obtains or is supplied with moisture (such as water, humidity, or precipitation) from another entity.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f8f71a08190a440ff19dcc65312 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:46 a.m.