Triple
T10340616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umklapp scattering |
E243118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electron scattering mechanism |
C27910
|
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: electron scattering mechanism Context triple: [Umklapp scattering, instanceOf, electron scattering mechanism]
-
A.
elastic scattering
Elastic scattering is a process in which particles collide and deflect from one another without any change in their internal states or total kinetic energy.
-
B.
hard scattering process
A hard scattering process is a high-momentum-transfer interaction between elementary particles, typically described by perturbative quantum field theory, that probes short-distance structure inside hadrons.
-
C.
inelastic light scattering process
An inelastic light scattering process is an interaction in which incident photons exchange energy with a material’s excitations (such as phonons or magnons), resulting in scattered photons with shifted frequencies that reveal information about the material’s internal structure and dynamics.
-
D.
scattering cross section
The scattering cross section is a measure of the effective area that quantifies the likelihood of a particle or wave being scattered by a target in a given interaction.
-
E.
high-energy particle interaction
A high-energy particle interaction is a physical event in which particles collide or interact at relativistic energies, producing new particles, radiation, and measurable signatures that probe fundamental forces and constituents of matter.
- F. None of above. chosen
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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:54 a.m.