Triple
T33115190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MURR |
E847441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | university research reactor |
C2094
|
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: university research reactor Context triple: [MURR, instanceOf, university research reactor]
-
A.
research reactor design
Research reactor design is the conceptual and engineering process of configuring a nuclear reactor’s core, systems, and safety features to produce controlled neutron fluxes for experiments, isotope production, and materials testing rather than for power generation.
-
B.
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.
-
C.
nuclear reactor
chosen
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.
-
D.
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.
-
E.
plutonium production reactor
A plutonium production reactor is a nuclear reactor specifically designed and operated to irradiate uranium fuel and efficiently generate plutonium-239 for use in nuclear weapons or reactor fuel.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:27 a.m.