Triple
T5877457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwinger effect |
E130661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vacuum instability |
C19056
|
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: vacuum instability Context triple: [Schwinger effect, instanceOf, vacuum instability]
-
A.
astrophysical instability
An astrophysical instability is a physical process in which small perturbations in an astronomical system grow over time, potentially leading to dramatic structural or dynamical changes such as star formation, disk fragmentation, or explosive events.
-
B.
astrophysical stability criterion
An astrophysical stability criterion is a theoretical condition or set of conditions used to determine whether an astronomical system (such as a star, disk, or gas cloud) will remain in equilibrium or undergo collapse, fragmentation, or other dynamical instabilities.
-
C.
boson
A boson is a particle that follows Bose-Einstein statistics and carries forces or forms collective quantum states, characterized by integer spin and the ability for multiple identical particles to occupy the same quantum state.
-
D.
scalar boson
A scalar boson is a particle with zero intrinsic spin that mediates interactions or manifests as a quantum excitation of a scalar field, such as the Higgs boson in the Standard Model.
-
E.
topological defect
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. 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:57 p.m.