Triple
T28433083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Provo River Project |
E715189
|
entity |
| Predicate | reservoirCapacityIncludes |
P79074
|
FINISHED |
| Object | Deer Creek Reservoir |
—
|
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: Deer Creek Reservoir | Statement: [Provo River Project, reservoirCapacityIncludes, Deer Creek Reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirCapacityIncludes Context triple: [Provo River Project, reservoirCapacityIncludes, Deer Creek Reservoir]
-
A.
reservoirTotalCapacity
Indicates the maximum volume of water that a reservoir is designed to hold when full.
-
B.
includesReservoir
chosen
Indicates that one entity contains or encompasses a reservoir as part of its structure, system, or area.
-
C.
reservoirGrossStorageCapacity_m3
Indicates the total volume of water a reservoir can hold when filled to its maximum designed storage level, measured in cubic meters.
-
D.
reservoirLiveStorageCapacity_m3
Indicates the volume of water that a reservoir can actively store and use, measured in cubic meters.
-
E.
reservoirLength
Indicates the measured longitudinal extent of a reservoir from one end to the other.
- 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 1:41 a.m.