Triple
T17969598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oahe Dam |
E449299
|
entity |
| Predicate | providesWaterSupplyTo |
P4360
|
FINISHED |
| Object | municipal users |
—
|
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: municipal users | Statement: [Oahe Dam, providesWaterSupplyTo, municipal users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesWaterSupplyTo Context triple: [Oahe Dam, providesWaterSupplyTo, municipal users]
-
A.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
B.
sourceOfWaterSupply
chosen
Indicates that one entity serves as the origin or provider of another entity’s water supply.
-
C.
waterSupplyShare
Indicates the proportion of a total water supply that is allocated to or used by a particular entity.
-
D.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
E.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b13b1b088190b7d71006b31e5cc3 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.