Triple
T31943676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V_cs |
E815590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | quark-mixing matrix element |
C20459
|
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: quark-mixing matrix element Context triple: [V_cs, instanceOf, quark-mixing matrix element]
-
A.
CP-violating system
A CP-violating system is a physical system whose interactions do not remain invariant under the combined operations of charge conjugation (C) and parity transformation (P), leading to observable asymmetries between matter and antimatter.
-
B.
parameter of the Standard Model
chosen
A parameter of the Standard Model is a fundamental numerical input—such as a particle mass, coupling constant, or mixing angle—whose value is not predicted by the theory itself but must be determined experimentally to fully specify its physical predictions.
-
C.
SU(3) generators
SU(3) generators are the eight linearly independent, traceless, Hermitian 3×3 matrices (often represented by the Gell-Mann matrices) that form a basis for the Lie algebra su(3), defining the infinitesimal symmetries of the SU(3) group.
-
D.
flavor oscillation system
A flavor oscillation system is a physical framework in which particles can change their type (or "flavor") over time or distance due to quantum mechanical mixing of their underlying states.
-
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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:06 a.m.