Triple
T19867175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaporizhzhia Nuclear Power Plant |
E477419
|
entity |
| Predicate | hasDryCaskStorage |
P90842
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zaporizhzhia Nuclear Power Plant, hasDryCaskStorage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDryCaskStorage Context triple: [Zaporizhzhia Nuclear Power Plant, hasDryCaskStorage, yes]
-
A.
onSiteDryCaskStorage
chosen
Indicates that spent nuclear fuel is stored in dry casks at the same site where it was generated or used.
-
B.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
C.
hasStorageRing
Indicates that one entity possesses or is equipped with a storage ring associated with it.
-
D.
hasStorageClass
Indicates that one entity is assigned or associated with a particular storage class that defines how its data is stored or managed.
-
E.
hasStorageFunction
Indicates that an entity serves to store, retain, or hold another entity or resource for later use.
- 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_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. |
Created at: April 10, 2026, 1:51 p.m.