Triple
T13460045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owyhee River |
E311336
|
entity |
| Predicate | OwyheeDamUse |
P40334
|
FINISHED |
| Object | irrigation water storage |
—
|
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 water storage | Statement: [Owyhee River, OwyheeDamUse, irrigation water storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OwyheeDamUse Context triple: [Owyhee River, OwyheeDamUse, irrigation water storage]
-
A.
reservoirUse
chosen
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
B.
downstreamReservoir
Indicates that one reservoir is located downstream of, and receives water flow from, another reservoir in a connected water system.
-
C.
reservoirCreatedByDam
Indicates that a reservoir exists as a result of being formed or impounded by a specific dam.
-
D.
hasLockAndDamSystem
Indicates that one entity possesses or is equipped with a system of locks and dams used to control water levels and facilitate navigation.
-
E.
watercourseHasDam
Indicates that a watercourse (such as a river or stream) has a dam constructed on or across it.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0c177081909178dec61b09c278 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03dcd0c8190a8927eb4eaad1c45 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.