Triple
T15891792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Western Canal |
E385341
|
entity |
| Predicate | waterControl |
P21624
|
FINISHED |
| Object | regulated by barrage gates at Sukkur |
—
|
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: regulated by barrage gates at Sukkur | Statement: [North Western Canal, waterControl, regulated by barrage gates at Sukkur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterControl Context triple: [North Western Canal, waterControl, regulated by barrage gates at Sukkur]
-
A.
waterInput
Indicates that an entity receives or is supplied with water from another source or system.
-
B.
managesWaterFrom
chosen
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
C.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
D.
hasWaterControlRole
Indicates that an entity holds a role or responsibility related to managing, regulating, or overseeing water resources or water systems.
-
E.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.