Triple
T20987984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permanent Okavango River Basin Water Commission |
E516941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transboundary water commission |
C37175
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: transboundary water commission Context triple: [Permanent Okavango River Basin Water Commission, instanceOf, transboundary water commission]
-
A.
river basin organization
A river basin organization is an institutional body responsible for coordinating the management, development, and protection of water and related resources within a defined river basin across sectors and jurisdictions.
-
B.
cross-border lake
A cross-border lake is a body of water whose surface and/or basin is geographically shared and jointly influenced by two or more sovereign countries.
-
C.
river commission
chosen
A river commission is an authoritative body responsible for managing, regulating, and coordinating the use, conservation, and development of a river and its surrounding resources, often across multiple jurisdictions.
-
D.
water resources management agreement
A water resources management agreement is a formal arrangement between parties that defines rights, responsibilities, and coordinated actions for the sustainable allocation, use, protection, and monitoring of shared water resources.
-
E.
water transfer project
A water transfer project is a large-scale infrastructure system designed to move water from regions of surplus to regions of deficit through canals, pipelines, tunnels, and related facilities to meet agricultural, industrial, and domestic needs.
- F. None of above.
Provenance (1 batch)
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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:49 p.m.