Triple
T4361035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel–Jordan Joint Water Committee |
E98660
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bilateral water management body |
C2067
|
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: bilateral water management body Context triple: [Israel–Jordan Joint Water Committee, instanceOf, bilateral water management body]
-
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.
water management structure
A water management structure is a constructed facility or system designed to control, store, convey, or regulate the quantity and movement of water in natural or built environments.
-
C.
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.
-
D.
intergovernmental legal body
chosen
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
E.
interstate boundary river
An interstate boundary river is a natural watercourse whose channel or thalweg forms all or part of the legal border between two or more states or equivalent political jurisdictions.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:16 p.m.