Triple
T365098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandrasekhar–Friedman–Schutz instability |
E7942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysical instability |
C1390
|
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 instability Context triple: [Chandrasekhar–Friedman–Schutz instability, instanceOf, astrophysical instability]
-
A.
astronomical object
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.
gravitational collapse model
A gravitational collapse model is a theoretical framework that describes how matter in astrophysical systems contracts under its own gravity, potentially leading to the formation of dense objects such as stars, black holes, or compact stellar remnants.
-
C.
cosmological collapse solution
A cosmological collapse solution is a spacetime model in general relativity or cosmology in which the universe (or a region of it) evolves from expansion or equilibrium into a contracting phase that culminates in a singularity or high-density end state.
-
D.
astronomical observatory
An astronomical observatory is a facility equipped with specialized instruments and structures designed to observe, record, and analyze celestial objects and phenomena.
-
E.
planet
A planet is a large, roughly spherical celestial body that orbits a star, has sufficient mass for its gravity to maintain hydrostatic equilibrium, and has cleared its orbital neighborhood of other debris.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.