Triple
T28622051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov loop |
E724409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gauge-invariant observable |
C54343
|
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-invariant observable Context triple: [Polyakov loop, instanceOf, gauge-invariant observable]
-
A.
gauge theory identity
A gauge theory identity is a mathematical relation that expresses how physical quantities or fields remain invariant or transform consistently under local gauge symmetry transformations in a gauge theory.
-
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.
renormalizable gauge
A renormalizable gauge is a choice of gauge-fixing in a gauge theory that preserves renormalizability, ensuring that all infinities arising in quantum corrections can be absorbed into a finite set of parameters.
-
D.
gauge-fixing scheme
A gauge-fixing scheme is a systematic prescription for selecting a unique representative from each equivalence class of gauge-related field configurations to eliminate redundant gauge degrees of freedom in a gauge theory.
-
E.
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.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:34 a.m.