Triple
T8727660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minidoka Dam |
E207169
|
entity |
| Predicate | hasHydraulicHead |
P84295
|
FINISHED |
| Object | approximately 24 meters |
—
|
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: approximately 24 meters | Statement: [Minidoka Dam, hasHydraulicHead, approximately 24 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydraulicHead Context triple: [Minidoka Dam, hasHydraulicHead, approximately 24 meters]
-
A.
hasHeadwaterStatus
Indicates that a water body holds the status of being a headwater or source segment within a hydrological system.
-
B.
hasHydrologicalType
Indicates a relationship where an entity is classified according to its hydrological category or type (e.g., river, lake, aquifer).
-
C.
hasAquifer
Indicates that one entity possesses, contains, or overlies an aquifer associated with it.
-
D.
hasHydrologicalRegime
Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
-
E.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
- F. None of above. chosen
Provenance (4 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d1890e0819088b271db51faa738 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:37 p.m.