Triple
T10376322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yang–Mills theory |
E244516
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-abelian gauge theory |
C1454
|
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: non-abelian gauge theory Context triple: [Yang–Mills theory, instanceOf, non-abelian gauge theory]
-
A.
non-Abelian gauge group
A non-Abelian gauge group is a symmetry group of a gauge theory whose elements do not commute, leading to self-interacting gauge fields and rich interaction structures such as those in the strong and weak nuclear forces.
-
B.
gauge theory
chosen
A gauge theory is a type of field theory in which the laws of physics are invariant under continuous local transformations of certain internal symmetries, leading to the introduction of gauge fields that mediate fundamental interactions.
-
C.
electroweak theory
Electroweak theory is a unified quantum field theory that describes the electromagnetic and weak nuclear forces as different manifestations of a single SU(2)×U(1) gauge symmetry, spontaneously broken via the Higgs mechanism.
-
D.
gauge boson
A gauge boson is a force-carrying elementary particle that mediates interactions between matter particles in accordance with the symmetries of a gauge field theory.
-
E.
anomaly cancellation mechanism
An anomaly cancellation mechanism is a theoretical consistency requirement in quantum field theories whereby contributions from different fields or symmetries are arranged to exactly cancel gauge or gravitational anomalies, ensuring the preservation of gauge invariance and unitarity.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:02 p.m.