Triple
T36870540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPST instanton |
E911211
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | solution of Yang–Mills equations |
C19902
|
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: solution of Yang–Mills equations Context triple: [BPST instanton, instanceOf, solution of Yang–Mills equations]
-
A.
solution of classical field equations
chosen
A solution of classical field equations is a specific configuration of fields in space and time that satisfies the governing differential equations and boundary/initial conditions of a classical field theory.
-
B.
magnetic monopole solution
A magnetic monopole solution is a theoretical field configuration in gauge or electromagnetic theory that describes an isolated, point-like source of magnetic charge consistent with the underlying equations of motion.
-
C.
system of coupled field equations
A system of coupled field equations is a set of interdependent mathematical relations describing how multiple fields evolve together in space and time, each influencing and being influenced by the others.
-
D.
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.
-
E.
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.
- 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_69f76e80f6f0819091cba8e19b269615 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.