Triple
T1979367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daiichi nuclear disaster |
E42988
|
entity |
| Predicate | notableSubstanceReleased |
P35724
|
FINISHED |
| Object | iodine-131 |
—
|
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: iodine-131 | Statement: [Fukushima Daiichi nuclear disaster, notableSubstanceReleased, iodine-131]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSubstanceReleased Context triple: [Fukushima Daiichi nuclear disaster, notableSubstanceReleased, iodine-131]
-
A.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
B.
gasReleased
Indicates that a gas is emitted or discharged from a source into its surrounding environment.
-
C.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
D.
notableFire
Indicates that a significant or historically important fire event is associated with the subject.
-
E.
containsChemical
Indicates that one entity includes or has within it a specified chemical substance.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb96f932881908bebfc4176fda7c0 |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb798d288819083132cf14605bd02 |
completed | March 7, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69abb96e07c08190beed60096e9d71b4 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:36 p.m.