Triple
T25717616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Nuclear Fuel Market conference |
E644902
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear energy event |
C50684
|
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 energy event Context triple: [World Nuclear Fuel Market conference, instanceOf, nuclear energy event]
-
A.
nuclear event severity rating
A nuclear event severity rating is a standardized classification that quantifies the safety impact and seriousness of nuclear and radiological incidents based on factors such as radiation release, exposure, and damage to people and the environment.
-
B.
national nuclear energy program
A national nuclear energy program is a coordinated governmental initiative that plans, develops, regulates, and operates nuclear technologies to generate electricity and support related industrial, scientific, and security objectives.
-
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 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.
-
E.
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.
- F. None of above. chosen
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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 9:46 p.m.