Triple
T868876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Bubble |
E18766
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cavity in the interstellar medium |
C596
|
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: cavity in the interstellar medium Context triple: [Local Bubble, instanceOf, cavity in the interstellar medium]
-
A.
astronomical object
chosen
An astronomical object is any naturally occurring physical entity in space, such as stars, planets, moons, asteroids, comets, or galaxies, that exists within the universe.
-
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.
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.
-
D.
planetary system
A planetary system is a collection of planets and other celestial bodies, such as moons, asteroids, and comets, gravitationally bound to a central star or stars.
-
E.
intensity interferometry effect
The intensity interferometry effect is the phenomenon where correlations in the intensity fluctuations of light (or other waves) measured at separated detectors reveal information about the spatial structure and coherence properties of the source.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.