Triple
T23836890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casimir effect |
E590880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vacuum fluctuation effect |
C19055
|
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 fluctuation effect Context triple: [Casimir effect, instanceOf, vacuum fluctuation effect]
-
A.
vacuum instability
Vacuum instability is the phenomenon in quantum field theory where a seemingly stable vacuum state can spontaneously transition to a lower-energy configuration, potentially triggering dramatic changes in the structure and properties of the universe.
-
B.
nonperturbative effect
chosen
A nonperturbative effect is a physical phenomenon that cannot be captured by any finite-order expansion in a small parameter (such as a coupling constant) and instead arises from intrinsically non-linear or exponentially suppressed contributions, like instantons or tunneling.
-
C.
photon correlation effect
Photon correlation effect is the phenomenon where statistical correlations between detected photons reveal underlying properties of a light source, such as coherence, quantum statistics, and emission dynamics.
-
D.
quantum effect near event horizon
A quantum effect near an event horizon is a phenomenon arising from quantum field fluctuations in the intense gravitational boundary of a black hole, leading to processes such as particle creation and Hawking radiation.
-
E.
fluctuation test
A fluctuation test is an experimental method used to determine whether mutations arise spontaneously and randomly or are induced by selective conditions, typically by analyzing variation in mutant counts across parallel cultures.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:07 p.m.