Triple
T30962762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bondi–Metzner–Sachs symmetry |
E788872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | asymptotic symmetry group |
C20392
|
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: asymptotic symmetry group Context triple: [Bondi–Metzner–Sachs symmetry, instanceOf, asymptotic symmetry group]
-
A.
spacetime symmetry group
chosen
A spacetime symmetry group is the mathematical group of transformations (such as translations, rotations, and boosts) that leave the physical laws or geometric structure of spacetime invariant.
-
B.
symmetry in quantum field theory
Symmetry in quantum field theory is a transformation of fields that leaves the action or Lagrangian invariant, leading to conserved quantities and powerful constraints on particle interactions and dynamics.
-
C.
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.
-
D.
electric–magnetic duality
Electric–magnetic duality is a symmetry in certain physical theories that interchanges electric and magnetic fields or charges, often mapping a strongly coupled description of a system to a weakly coupled one while preserving its physical content.
-
E.
one-parameter Lie group
A one-parameter Lie group is a smooth group homomorphism from the real numbers (under addition) into a Lie group, describing a continuous one-dimensional family of group elements parameterized by a real variable.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.