Triple
T32037175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRC Reactor Oversight Process |
E818126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear reactor safety oversight process |
C60459
|
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 safety oversight process Context triple: [NRC Reactor Oversight Process, instanceOf, nuclear reactor safety oversight process]
-
A.
reactor safety research program
A reactor safety research program is an organized, systematic effort to study, evaluate, and improve the safety, reliability, and risk management of nuclear reactors through experiments, modeling, and analysis.
-
B.
nuclear safety standard series
A nuclear safety standard series is a structured collection of coordinated regulations, guidelines, and technical criteria designed to ensure the safe design, operation, and decommissioning of nuclear facilities and activities.
-
C.
nuclear reactor technology
Nuclear reactor technology encompasses the design, operation, and safety systems of devices that control nuclear fission reactions to reliably produce usable energy.
-
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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.