Triple
T3576629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethe–Weizsäcker cycle |
E75704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stellar nuclear fusion process |
C5339
|
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: stellar nuclear fusion process Context triple: [Bethe–Weizsäcker cycle, instanceOf, stellar nuclear fusion process]
-
A.
nucleosynthesis process
chosen
A nucleosynthesis process is a physical mechanism in which atomic nuclei are formed or transformed, typically through nuclear reactions in stars, stellar explosions, or the early universe.
-
B.
nuclear reaction mechanism
A nuclear reaction mechanism is the detailed sequence of interactions and intermediate steps by which incident particles induce changes in a nucleus, leading to specific reaction products and energy release.
-
C.
fusion energy research facility
A fusion energy research facility is a specialized scientific complex where researchers design, build, and operate advanced experimental systems to achieve and study controlled nuclear fusion as a potential source of large-scale, low-carbon power.
-
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 pulse propulsion system
A nuclear pulse propulsion system is a spacecraft propulsion method that generates thrust by detonating a series of small nuclear explosives behind the vehicle and transferring the resulting impulse through a robust pusher plate and shock-absorbing structure.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:21 p.m.