Triple
T31016297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daini Nuclear Power Plant |
E790334
|
entity |
| Predicate | experiencedStationBlackout |
P14197
|
FINISHED |
| Object | partial |
—
|
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: partial | Statement: [Fukushima Daini Nuclear Power Plant, experiencedStationBlackout, partial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedStationBlackout Context triple: [Fukushima Daini Nuclear Power Plant, experiencedStationBlackout, partial]
-
A.
lostPowerInEvent
Indicates that an entity ceased to have power or electricity as a result of a specific event.
-
B.
lostPowerDuring
chosen
Indicates that an entity ceased to have electrical or functional power at some time during a specified event or interval.
-
C.
lostPowerThrough
Indicates that an entity ceased to have power, authority, or control as a result of another specified entity or factor.
-
D.
hasMemoryBlackouts
Indicates that an entity experiences episodes of lost or impaired memory for certain periods or events.
-
E.
lostTemporalPower
Indicates that an entity has ceased to hold or exercise secular or time-bound authority or control it previously possessed.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:57 p.m.