Triple
T28433088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provo River Project |
E715189
|
entity |
| Predicate | providesMunicipalWaterTo |
P4360
|
FINISHED |
| Object | Salt Lake County |
—
|
NE NERFINISHED |
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: Salt Lake County | Statement: [Provo River Project, providesMunicipalWaterTo, Salt Lake County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesMunicipalWaterTo Context triple: [Provo River Project, providesMunicipalWaterTo, Salt Lake County]
-
A.
waterSupplyPopulationServed
Indicates the number of people that are provided with or served by a particular water supply system.
-
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.
hasWaterServiceFrom
Indicates that one entity receives its water supply or water-related services from another entity.
-
E.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 1:41 a.m.