Physical Transformation AtlasPTA
Claim · claim:thermogalvanic-drives

Temperature gradient —drives→ Thermogalvanic effect

The atlas records this claim as established: a temperature gradient drives the thermogalvanic effect under the conditions below.

establishedK6 · working transducerledger thermal → electrical · loss to thermalno record-level review date

Exploreconditions · relation · evidence · matrix context · uses · cite

2cited sources10enumerated routes using it1routes with composition evidence1recorded pathways

Conditions

  • two identical electrodes in one redox electrolyte held at different temperatures
  • a redox couple with large reaction entropy (ferri/ferrocyanide gives ≈ −1.4 mV/K)
regime: liquid · aqueous medium required · temperature gradient required

Constitutive relation

ΔE = (ΔS_rxn / nF) · ΔT

input Temperature differenceoutput Electric potentialthermogalvanic Seebeck coefficient [V/K]

Evidence · 2

  1. [1]
    T. I. Quickenden, Y. Mua. A review of power generation in aqueous thermogalvanic cells (1995)
    Journal of the Electrochemical Society 142, 3985 · doi:10.1149/1.2048446 · crossref ✓ 2026-09-19 · record
  2. [2]
    M. F. Dupont, D. R. MacFarlane, J. M. Pringle. Thermo-electrochemical cells for waste heat harvesting – progress and perspectives (2017)
    Chemical Communications 53, 6288–6302 · doi:10.1039/C7CC02160G · crossref ✓ 2026-09-19 · record

Matrix cells this relation feeds

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

Uses of this claim

recorded pathways · 1
other enumerated routes · 9

Cite this claim

Physical Transformation Atlas (2026). claim claim:thermogalvanic-drives: Temperature gradient —drives→ Thermogalvanic effect. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/thermogalvanic-drives

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.