Triple
T35225750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzyaloshinskii–Moriya interaction |
E1017089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | antisymmetric exchange interaction |
C61796
|
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: antisymmetric exchange interaction Context triple: [Dzyaloshinskii–Moriya interaction, instanceOf, antisymmetric exchange interaction]
-
A.
antisymmetric wavefunction
An antisymmetric wavefunction is a quantum mechanical state that changes sign upon exchange of any two identical fermions, ensuring compliance with the Pauli exclusion principle.
-
B.
magnetic interaction
Magnetic interaction is the force and influence that arises between moving electric charges, magnetic dipoles, or magnetic fields, governing phenomena such as attraction, repulsion, and torque in magnetic systems.
-
C.
spin model
A spin model is a mathematical representation of interacting discrete magnetic moments (spins) on a lattice or graph, used to study phase transitions and collective behavior in statistical and condensed matter physics.
-
D.
exchange interaction
chosen
An exchange interaction is a quantum mechanical effect arising from the indistinguishability and spin statistics of identical particles, leading to an effective coupling between their spins that underlies phenomena such as ferromagnetism and antiferromagnetism.
-
E.
anomalous magnetic moment
The anomalous magnetic moment is the small deviation of a particle’s actual magnetic moment from the value predicted by Dirac’s theory, arising from quantum radiative corrections and interactions with virtual particles.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.