Triple
T1189046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boundary Waters Treaty of 1909 |
E25315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water treaty |
C566
|
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: water treaty Context triple: [Boundary Waters Treaty of 1909, instanceOf, water treaty]
-
A.
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.
-
B.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
water management project
A water management project is an organized initiative that plans, develops, and operates systems and practices to sustainably collect, store, distribute, and protect water resources for human and environmental needs.
-
D.
watershed
A watershed is a land area that channels rainfall and snowmelt into streams and rivers, ultimately draining into a common outlet such as a larger river, lake, or ocean.
-
E.
water resources programme
A water resources programme is an organized set of policies, projects, and management activities aimed at sustainably developing, allocating, protecting, and monitoring water resources to meet environmental, social, and economic 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.