Triple
T23417053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevada water law doctrine of prior appropriation |
E560537
|
entity |
| Predicate | beneficialUseIncludes |
P7913
|
FINISHED |
| Object | irrigation |
—
|
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: irrigation | Statement: [Nevada water law doctrine of prior appropriation, beneficialUseIncludes, irrigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneficialUseIncludes Context triple: [Nevada water law doctrine of prior appropriation, beneficialUseIncludes, irrigation]
-
A.
benefitSharingIncludes
Indicates that the specified benefit-sharing arrangement encompasses or covers the referenced elements, parties, or mechanisms.
-
B.
eligibleUses
chosen
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
C.
assessesForUseIn
Indicates that one entity evaluates another entity to determine its suitability or appropriateness for a particular use or application.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
hasResearchUse
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a516d158819081e9710b4e372a21 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.