Triple
T29810998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniper Kraftwerke |
E756961
|
entity |
| Predicate | regulatesWaterLevelAt |
P130170
|
FINISHED |
| Object | Forggensee |
—
|
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: Forggensee | Statement: [Uniper Kraftwerke, regulatesWaterLevelAt, Forggensee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesWaterLevelAt Context triple: [Uniper Kraftwerke, regulatesWaterLevelAt, Forggensee]
-
A.
controlsWaterLevelOf
chosen
Indicates that one entity has the ability or authority to regulate or adjust the water level of another entity or system.
-
B.
hasNormalWaterLevel
Indicates that an entity’s water level is within the expected or standard range, neither abnormally high nor low.
-
C.
regulatesReservoir
Indicates that one entity controls, manages, or influences the operation, levels, or behavior of a reservoir.
-
D.
hasWaterLevelCharacteristic
Indicates that an entity is associated with a specific property, feature, or behavior related to its water level.
-
E.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 5:23 p.m.