Triple
T25598093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leesville Lake |
E641710
|
entity |
| Predicate | waterLevelRegime |
P50263
|
FINISHED |
| Object | hydro-peaking |
—
|
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: hydro-peaking | Statement: [Leesville Lake, waterLevelRegime, hydro-peaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterLevelRegime Context triple: [Leesville Lake, waterLevelRegime, hydro-peaking]
-
A.
waterLevelTrend
Indicates the direction and rate at which a body of water’s level is changing over time (e.g., rising, falling, or stable).
-
B.
currentHydrology
Indicates the present state or characteristics of water flow, distribution, and related hydrological conditions associated with an entity.
-
C.
hasHydrologicalRegime
chosen
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.
-
D.
waterLevelTransition
Indicates a change in water level from one state or value to another over time.
-
E.
seasonalFlow
Indicates that the flow or intensity of something varies in a recurring pattern according to the seasons.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 4:29 p.m.