Triple
T9296221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi Nuclear Power Plant |
E223644
|
entity |
| Predicate | reactor3StatusDuringAccident |
P87480
|
FINISHED |
| Object | core meltdown |
—
|
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: core meltdown | Statement: [Fukushima Daiichi Nuclear Power Plant, reactor3StatusDuringAccident, core meltdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reactor3StatusDuringAccident Context triple: [Fukushima Daiichi Nuclear Power Plant, reactor3StatusDuringAccident, core meltdown]
-
A.
PM-3AReactorOperationalUntil
Indicates that a specific PM-3A reactor remained in an operational state up to a given point in time.
-
B.
PM-3AReactorOperationalFrom
Indicates that a PM-3A nuclear reactor was in an operational state starting from a specified point in time.
-
C.
numberOfReactors
Indicates the quantity of reactors associated with or contained by a given entity.
-
D.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
-
E.
oneOfWorstNuclearAccidentsWith
Indicates that the subject is associated with another entity as being among the worst nuclear accidents together with it.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd089c9c588190967404c9eb938dfb |
completed | April 1, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:36 p.m.