Triple
T12205753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRX reactor accident of 1952 |
E290831
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear reactor accident |
C12005
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: nuclear reactor accident Context triple: [NRX reactor accident of 1952, instanceOf, nuclear reactor accident]
-
A.
nuclear reactor
A nuclear reactor is a controlled system that initiates, sustains, and regulates a nuclear fission chain reaction to produce heat, typically for generating electricity or powering ships.
-
B.
nuclear reactor project
A nuclear reactor project is a coordinated engineering and management effort to design, license, construct, operate, and eventually decommission a nuclear reactor facility for energy production, research, or other specialized applications.
-
C.
nuclear attack
A nuclear attack is a deliberate military or terrorist action involving the detonation or threatened use of nuclear weapons to cause massive destruction, casualties, and strategic disruption.
-
D.
nuclear power facility
A nuclear power facility is an industrial complex that generates electricity by harnessing heat produced from controlled nuclear fission reactions within reactors, converting it into mechanical and then electrical energy.
-
E.
radiological accident
chosen
A radiological accident is an unintended event involving the release, loss, misuse, or exposure to radioactive materials or radiation sources that poses actual or potential harm to people, property, or the environment.
- F. None of above.
Provenance (1 batch)
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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:51 p.m.