Triple
T6088202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 't Hooft–Polyakov monopoles |
E135691
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | magnetic monopole solution |
C19901
|
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: magnetic monopole solution Context triple: ['t Hooft–Polyakov monopoles, instanceOf, magnetic monopole solution]
-
A.
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.
-
B.
quantized magnetic flux line
A quantized magnetic flux line is a discrete, tube-like region of magnetic flux whose strength is fixed in integer multiples of the fundamental flux quantum, typically occurring in superconductors or superfluids.
-
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.
solution in general relativity
A solution in general relativity is a specific spacetime metric (and accompanying matter fields, if any) that satisfies Einstein’s field equations for a given physical configuration or set of conditions.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:12 p.m.