Triple
T29810981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniper Kraftwerke |
E756961
|
entity |
| Predicate | operatesPowerPlantType |
P121503
|
FINISHED |
| Object | hydroelectric power plant |
—
|
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: hydroelectric power plant | Statement: [Uniper Kraftwerke, operatesPowerPlantType, hydroelectric power plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesPowerPlantType Context triple: [Uniper Kraftwerke, operatesPowerPlantType, hydroelectric power plant]
-
A.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
B.
operatedPlantType
chosen
Indicates that an entity operates or manages a plant (facility) of a specified type.
-
C.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
-
D.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
E.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving 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_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: April 29, 2026, 5:23 p.m.