Triple
T13628808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malheur River |
E325657
|
entity |
| Predicate | watershedUse |
P25275
|
FINISHED |
| Object | livestock watering |
—
|
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: livestock watering | Statement: [Malheur River, watershedUse, livestock watering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watershedUse Context triple: [Malheur River, watershedUse, livestock watering]
-
A.
hasWatershedUse
chosen
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
B.
reservoirUse
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
C.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
-
D.
watershedType
Indicates the classification or category of a watershed associated with an entity (e.g., by hydrologic, ecological, or management type).
-
E.
waterQualityUse
Indicates the way in which water quality is evaluated, classified, or applied for specific purposes or uses.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc60635d08190899806fe8936f02a |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe85e1c4819095194f4b7f9f6118 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:51 p.m.