Triple
T20870346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Fuzz |
E513871
|
entity |
| Predicate | nuclearAccidentInPlot |
P142174
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Super Fuzz, nuclearAccidentInPlot, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearAccidentInPlot Context triple: [Super Fuzz, nuclearAccidentInPlot, yes]
-
A.
oneOfWorstNuclearAccidentsWith
Indicates that the subject is associated with another entity as being among the worst nuclear accidents together with it.
-
B.
reactorInvolvedInAccident
Indicates that a specific reactor participated in, contributed to, or was directly affected by a particular accident event.
-
C.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
-
D.
numberOfFuelAssembliesInSpentFuelPoolAtAccident
Indicates the quantity of fuel assemblies that were present in the spent fuel pool at the time of the accident.
-
E.
fuelInReactorCoreAtTimeOfAccident
Indicates that a specified amount or type of fuel was present in the reactor core at the time the accident occurred.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c4637ec48190830023d20fb8124c |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:45 p.m.