Triple
T14318809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mono Lake water rights litigation |
E355026
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water rights litigation |
C13531
|
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 rights litigation Context triple: [Mono Lake water rights litigation, instanceOf, water rights litigation]
-
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.
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.
environmental law case
chosen
An environmental law case is a legal dispute or proceeding that involves the interpretation, application, or enforcement of laws and regulations designed to protect the environment and natural resources.
-
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 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.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.