Triple
T31346560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi Unit 1 |
E799461
|
entity |
| Predicate | coreDamageLevel |
P156947
|
FINISHED |
| Object | major core melt |
—
|
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: major core melt | Statement: [Fukushima Daiichi Unit 1, coreDamageLevel, major core melt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreDamageLevel Context triple: [Fukushima Daiichi Unit 1, coreDamageLevel, major core melt]
-
A.
coreDamageFrequency
Indicates how often damage occurs to the core component or central part of a system within a given context or time frame.
-
B.
damageRating
chosen
Indicates the assessed level or severity of damage associated with an entity or event.
-
C.
damageTo
Indicates a relationship where one entity causes harm, loss, or deterioration to another entity.
-
D.
damageAssessedBy
Indicates that the extent or nature of damage to something has been evaluated or determined by a particular agent or authority.
-
E.
damageScope
Indicates the extent or range of harm or impairment caused by an event, action, or condition.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f18afd48190bbbd54e517946499 |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.