Triple
T9583240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi Unit 3 |
E231223
|
entity |
| Predicate | postAccidentStatus |
P60365
|
FINISHED |
| Object | fuel debris present in reactor pressure vessel and containment |
—
|
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: fuel debris present in reactor pressure vessel and containment | Statement: [Fukushima Daiichi Unit 3, postAccidentStatus, fuel debris present in reactor pressure vessel and containment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postAccidentStatus Context triple: [Fukushima Daiichi Unit 3, postAccidentStatus, fuel debris present in reactor pressure vessel and containment]
-
A.
postDisasterStatus
chosen
Indicates the condition or state of an entity following the occurrence of a disaster.
-
B.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
C.
accident
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
D.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
-
E.
accidentPhase
Indicates the specific stage or phase of progression within an accident or incident event.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99cebaf081908033536a53fbf668 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59fd7408190b36831902e3f37f7 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:06 p.m.