Triple
T18773040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Cavity |
E459062
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysical cavity |
C16110
|
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: astrophysical cavity Context triple: [Local Cavity, instanceOf, astrophysical cavity]
-
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.
astronomical ceiling
An astronomical ceiling is an interior overhead surface decorated with representations of celestial bodies, constellations, or cosmic phenomena, often used to evoke the night sky or convey astronomical knowledge.
-
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.
interstellar bubble
chosen
An interstellar bubble is a vast, low-density cavity in the interstellar medium carved out by the stellar winds and radiation of massive stars, often bounded by a shell of compressed gas and dust.
-
E.
astronomical region
An astronomical region is a defined area of space, often delineated by physical, observational, or conceptual boundaries, used to study and describe the distribution and behavior of celestial objects and phenomena.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.