Triple
T35108031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kama River near Nizhnekamsk Reservoir |
E1013204
|
entity |
| Predicate | hasRegulatedFlowBy |
—
|
GENERATED |
| Object | Nizhnekamsk dam |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegulatedFlowBy Context triple: [Kama River near Nizhnekamsk Reservoir, hasRegulatedFlowBy, Nizhnekamsk dam]
-
A.
regulatesFlowFor
chosen
Indicates that one entity controls, directs, or manages the rate or movement of another entity’s flow.
-
B.
regulatesFlowBetween
Indicates a relationship where one entity controls, directs, or modulates the movement or transfer of something (such as material, energy, or information) between two other entities.
-
C.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by another entity.
-
D.
hasFlowRegime
Indicates that one entity is characterized by, or operates under, a particular pattern or regime of flow.
-
E.
regulateBy
Indicates that one entity exercises control, guidance, or governance over another entity’s behavior, operation, or state through rules, mechanisms, or constraints.
- F. None of above.
Provenance (1 batch)
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_69f76dd659d08190bcdc00d37caafb62 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.