Triple
T17105572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 't Hooft–Veltman gauge |
E415090
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gauge-fixing scheme |
C38837
|
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: gauge-fixing scheme Context triple: ['t Hooft–Veltman gauge, instanceOf, gauge-fixing scheme]
-
A.
regularization scheme in quantum field theory
A regularization scheme in quantum field theory is a systematic procedure for modifying divergent integrals or sums—typically by introducing an auxiliary parameter or cutoff—so that they become finite and mathematically well-defined while preserving as much of the theory’s symmetry and structure as possible.
-
B.
gauge theory
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.
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.
-
D.
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.
-
E.
standardization scheme
A standardization scheme is a structured framework of rules, formats, and procedures designed to ensure consistency, compatibility, and interoperability across systems, processes, or data.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.