Triple
T5487129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truckee River Operating Agreement |
E123610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interstate water allocation agreement |
C3447
|
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: interstate water allocation agreement Context triple: [Truckee River Operating Agreement, instanceOf, interstate water allocation agreement]
-
A.
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.
-
B.
interstate compact
chosen
An interstate compact is a formal, legally binding agreement between two or more U.S. states, approved by their legislatures (and often by Congress), to cooperatively address shared problems or manage common resources.
-
C.
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.
-
D.
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.
-
E.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:10 p.m.