Triple
T19867194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaporizhzhia Nuclear Power Plant |
E477419
|
entity |
| Predicate | backupPowerSource |
P137634
|
FINISHED |
| Object | diesel generators |
—
|
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: diesel generators | Statement: [Zaporizhzhia Nuclear Power Plant, backupPowerSource, diesel generators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backupPowerSource Context triple: [Zaporizhzhia Nuclear Power Plant, backupPowerSource, diesel generators]
-
A.
hasBackupBattery
Indicates that an entity is equipped with an additional battery intended to provide power when the primary power source is unavailable or fails.
-
B.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
secondaryBattery
Indicates that an entity has a secondary battery system or backup power source in addition to its primary battery.
-
D.
batterySupplier
Indicates that one entity serves as the supplier or provider of batteries to another entity.
-
E.
maintainsPowerThrough
Indicates that one entity preserves or secures its authority, control, or dominance by means of another entity or specified mechanism.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658a0a7288190a82b85e3ae056d6b |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.