Triple
T28078616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Basin |
E709614
|
entity |
| Predicate | waterRightsSystem |
P26835
|
FINISHED |
| Object | prior appropriation doctrine |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: prior appropriation doctrine | Statement: [Upper Basin, waterRightsSystem, prior appropriation doctrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterRightsSystem Context triple: [Upper Basin, waterRightsSystem, prior appropriation doctrine]
-
A.
waterRight
Indicates a legal or recognized entitlement that one party has to use or access water from a particular source under specified conditions.
-
B.
waterRightsHolder
Indicates that the subject holds legal rights to use or control water resources associated with the object.
-
C.
hasWaterRightsSystem
chosen
Indicates that an entity possesses or is governed by a defined system regulating legal rights to use water resources.
-
D.
settlesWaterRightsOf
Indicates that one party resolves or determines the allocation or ownership of water usage rights involving another party.
-
E.
waterSharingDispute
Indicates a conflict or disagreement between parties over the allocation, use, or control of water resources.
- F. None of above.
Provenance (3 batches)
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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 8:50 p.m.