Triple
T28078597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Basin |
E709614
|
entity |
| Predicate | containsMajorReservoir |
P79074
|
FINISHED |
| Object | Flaming Gorge 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: Flaming Gorge Reservoir | Statement: [Upper Basin, containsMajorReservoir, Flaming Gorge Reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMajorReservoir Context triple: [Upper Basin, containsMajorReservoir, Flaming Gorge Reservoir]
-
A.
hasMajorReservoir
Indicates that an entity possesses or is associated with a primary or significant reservoir (such as a large storage or accumulation of a resource).
-
B.
majorReservoir
Indicates that one entity functions as a primary or significant water-storage reservoir associated with another entity.
-
C.
includesReservoir
chosen
Indicates that one entity contains or encompasses a reservoir as part of its structure, system, or area.
-
D.
isReservoir
Indicates that one entity functions as a storage or holding container (often for fluids or resources) for another entity.
-
E.
usesReservoir
Indicates that one entity draws upon, depends on, or operates using a particular reservoir as a resource or source.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: April 27, 2026, 8:50 p.m.