Triple
T19961404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas v. New Mexico |
E479822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interstate water rights case |
C38121
|
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 rights case Context triple: [Texas v. New Mexico, instanceOf, interstate water rights case]
-
A.
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.
-
B.
water resources development act
The Water Resources Development Act is a recurring United States federal law that authorizes and guides the planning, construction, and maintenance of water resources projects such as navigation, flood control, and ecosystem restoration, primarily carried out by the U.S. Army Corps of Engineers.
-
C.
water management law
chosen
Water management law is the body of legal rules and principles governing the allocation, use, protection, and regulation of water resources among public and private users.
-
D.
Erie doctrine case
An Erie doctrine case is a federal court lawsuit in which the court must decide whether to apply state substantive law or federal law/procedural rules under the principles established in Erie Railroad Co. v. Tompkins and its progeny.
-
E.
interstate council
An interstate council is a formal collaborative body composed of representatives from multiple states or jurisdictions that coordinates policies, resolves shared issues, and facilitates joint decision-making across state boundaries.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:54 p.m.