Triple

T6088205
Position Surface form Disambiguated ID Type / Status
Subject 't Hooft–Polyakov monopoles E135691 entity
Predicate instanceOf P0 FINISHED
Object non-abelian monopole C9631 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 monopole
Context triple: ['t Hooft–Polyakov monopoles, instanceOf, non-abelian monopole]
  • 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. non-topological soliton
    A non-topological soliton is a stable, localized field configuration whose stability arises from conserved charges or dynamical effects rather than from the topology of the underlying field space.
  • C. 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.
  • D. non-singular black hole model
    A non-singular black hole model is a theoretical description of a black hole whose core avoids the classical spacetime singularity, typically by invoking modified gravity or quantum effects that yield a finite, regular interior geometry.
  • E. topological defect chosen
    A topological defect is a stable, localized irregularity in an ordered medium or field configuration that arises because the system’s topology prevents it from being continuously transformed into a uniform state.
  • 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_69c0087bcc788190b20f093d3a6c60ec completed March 22, 2026, 3:19 p.m.
Created at: March 22, 2026, 4:12 p.m.