Triple
T25820650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holmboe instability |
E650394
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shear instability |
C51039
|
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: shear instability Context triple: [Holmboe instability, instanceOf, shear instability]
-
A.
rotational instability in stars
Rotational instability in stars is a dynamical condition where differential rotation or excessive spin causes internal layers to become unstable, leading to mixing, angular momentum redistribution, and potentially large-scale structural changes or mass loss.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
strike-slip fault
A strike-slip fault is a fracture in the Earth's crust where blocks of rock slide horizontally past each other, primarily due to shear stress.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:29 a.m.