Physical Transformation AtlasPTA
Phenomenon · phenomenon:betavoltaic-effect

Betavoltaic effect

Beta particles absorbed in a semiconductor junction create thousands of electron–hole pairs each, which the junction separates. A nuclear flux becomes a small, decades-long current.

Nuclear physicsfirst reported 1954also: electron-voltaic effect

Atlas record: 5 claims reference this phenomenon — 5 established.

Explorerelations · matrix context · routes · sources · cite

conditions: solid · semiconductor required · radioisotope required
5claims1enumerated routes1routes with complete-composition evidence0candidate routes not searched2cited sources

Relations

drives · 1
Beta particles—drives→Betavoltaic effectestablished
  • a beta source (tritium, Ni-63, Pm-147) on or in a semiconductor junction; particle energy below the lattice-damage threshold
produces · 1
Betavoltaic effect—produces→Electron–hole pairsestablished
member of · 1
Betavoltaic effect—member of→Radiovoltaicestablished
implemented by · 1
Betavoltaic effect—implemented by→Betavoltaic cellestablished
observed in · 1
Betavoltaic effect—observed in→Crystalline siliconestablished

Matrix context

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

family: Radiovoltaic (C.26)

Enumerated routes through this · 1

Cited sources · 2

  1. [1]
    P. Rappaport. The electron-voltaic effect in p-n junctions induced by beta-particle bombardment (1954)
    Physical Review 93, 246 · doi:10.1103/PhysRev.93.246.2 · crossref ✓ 2026-09-19 · record
  2. [2]
    M. A. Prelas, et al.. A review of nuclear batteries (2014)
    Progress in Nuclear Energy 75, 117–148 · doi:10.1016/j.pnucene.2014.04.007 · crossref ✓ 2026-09-19 · record

Cite this entity

Physical Transformation Atlas (2026). entity phenomenon:betavoltaic-effect: Betavoltaic effect. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/phenomenon/betavoltaic-effect

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.