Triple
T35249991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schuster–Schwarzschild theorem |
E1018069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysics theorem |
C47154
|
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: astrophysics theorem Context triple: [Schuster–Schwarzschild theorem, instanceOf, astrophysics theorem]
-
A.
theorem in theoretical physics
chosen
A theorem in theoretical physics is a rigorously proven statement, derived from fundamental physical principles and mathematical formalism, that holds universally within the specified theoretical framework.
-
B.
astronomical theory
An astronomical theory is a coherent, scientifically grounded framework that explains and predicts phenomena in the universe, such as the motions, origins, and properties of celestial bodies and cosmic structures.
-
C.
theorem in relativistic cosmology
A theorem in relativistic cosmology is a rigorously proven statement, derived from the Einstein field equations and related physical assumptions, that characterizes the large-scale structure, dynamics, or evolution of spacetime and matter in the universe.
-
D.
astrophysics theory program
An astrophysics theory program is an academic or research initiative focused on developing and applying theoretical models and computational methods to understand the physical processes governing astronomical objects and the universe.
-
E.
astronomical law
An astronomical law is a fundamental principle or rule, derived from observation and theory, that describes consistent patterns and relationships governing celestial bodies and cosmic 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.