Triple
T31016300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Daini Nuclear Power Plant |
E790334
|
entity |
| Predicate | INESRating2011Accident |
P87477
|
FINISHED |
| Object | Level 3 |
—
|
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: Level 3 | Statement: [Fukushima Daini Nuclear Power Plant, INESRating2011Accident, Level 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: INESRating2011Accident Context triple: [Fukushima Daini Nuclear Power Plant, INESRating2011Accident, Level 3]
-
A.
2011AccidentFatalities
Indicates the number of people who died in accidents that occurred in the year 2011.
-
B.
injuredIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or action.
-
C.
numberOfFatalAccidents
Indicates the total count of accidents within a given context that resulted in at least one fatality.
-
D.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
E.
accidentSeverity
chosen
Indicates the level or degree of seriousness associated with an accident.
- 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.