Triple
T10695973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukushima Prefecture |
E252139
|
entity |
| Predicate | nuclearAccidentDate |
P27390
|
FINISHED |
| Object | 2011-03-11 |
—
|
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: 2011-03-11 | Statement: [Fukushima Prefecture, nuclearAccidentDate, 2011-03-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearAccidentDate Context triple: [Fukushima Prefecture, nuclearAccidentDate, 2011-03-11]
-
A.
missionAccidentDate
Indicates the date on which an accident occurred during or in relation to a mission.
-
B.
numberOfFuelAssembliesInSpentFuelPoolAtAccident
Indicates the quantity of fuel assemblies that were present in the spent fuel pool at the time of the accident.
-
C.
fuelInReactorCoreAtTimeOfAccident
Indicates that a specified amount or type of fuel was present in the reactor core at the time the accident occurred.
-
D.
dateOfTragedy
chosen
Indicates the specific calendar date on which a tragic event occurred.
-
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.
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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd3af5248190ab807965255e9ad2 |
completed | April 9, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:11 p.m.