Triple
T13528989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvant-1 |
E323083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astrophysics module |
C33160
|
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 module Context triple: [Kvant-1, instanceOf, astrophysics module]
-
A.
astrophysical model
An astrophysical model is a theoretical or computational framework that describes and predicts the physical processes, structures, and evolution of astronomical objects and phenomena in the universe.
-
B.
astrophysics program office
An astrophysics program office is an organizational unit that plans, coordinates, and manages astrophysics research missions, funding, and related scientific activities within an institution or agency.
-
C.
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.
-
D.
NASA astrophysics program
A NASA astrophysics program is an organized set of space- and ground-based research activities, missions, and supporting infrastructure dedicated to observing the universe, advancing our understanding of fundamental astrophysical processes, and enabling scientific discovery through data collection, analysis, and technology development.
-
E.
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.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.