Physical Transformation AtlasPTA
Claim · claim:sse-drives

Temperature gradient —drives→ Spin Seebeck effect

The atlas records this claim as replicated: a temperature gradient drives the spin Seebeck effect under the conditions below.

replicatedK4 · experimentally observedledger thermal → spin · loss to thermalno record-level review date

Exploreconditions · evidence · matrix context · uses · cite

4cited sources9enumerated routes using it1routes with composition evidence1recorded pathways

Conditions

  • a magnetised ferromagnet, metallic or insulating (YIG), under a temperature gradient
  • an adjacent spin sink (heavy-metal layer) is needed for the usual electrical detection through inverse spin Hall conversion, not for the spin-Seebeck response itself
regime: solid · ferromagnet required · temperature gradient required

Evidence · 4

  1. [1]
    K. Uchida, et al.. Observation of the spin Seebeck effect (2008)
    Nature 455, 778–781 · doi:10.1038/nature07321 · crossref ✓ 2026-09-19 · record
  2. [2]
    K. Uchida, et al.. Spin Seebeck insulator (2010)
    Nature Materials 9, 894–897 · doi:10.1038/nmat2856 · crossref ✓ 2026-09-19 · record
  3. [3]
    G. E. W. Bauer, E. Saitoh, B. J. van Wees. Spin caloritronics (2012)
    Nature Materials 11, 391–399 · doi:10.1038/nmat3301 · crossref ✓ 2026-09-19 · record
  4. [4]
    M. Weiler et al.. Experimental test of the spin mixing interface conductivity concept (2013)
    Physical Review Letters 111, 176601 · doi:10.1103/PhysRevLett.111.176601 · 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 · 8

Cite this claim

Physical Transformation Atlas (2026). claim claim:sse-drives: Temperature gradient —drives→ Spin Seebeck effect. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/sse-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.