Triple
T19281813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGP-6 at Bilibino Nuclear Power Plant |
E482206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet-designed reactor |
C2097
|
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: Soviet-designed reactor Context triple: [EGP-6 at Bilibino Nuclear Power Plant, instanceOf, Soviet-designed reactor]
-
A.
Generation III+ reactor
A Generation III+ reactor is an advanced nuclear power plant design that enhances Generation III features with improved safety systems, higher efficiency, and longer operational lifetimes, often incorporating passive safety and standardized modular construction.
-
B.
Soviet design bureau
A Soviet design bureau was a state-controlled, specialized engineering and research organization responsible for conceiving, developing, and prototyping advanced military and industrial technologies within the centrally planned Soviet system.
-
C.
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.
-
D.
water-cooled reactor
chosen
A water-cooled reactor is a nuclear reactor that uses water as both a coolant to remove heat from the reactor core and often as a moderator to slow down neutrons, enabling a controlled fission chain reaction.
-
E.
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.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:30 p.m.