Triple
T7869300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theoretical Astrophysics Division |
E182698
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theoretical astrophysics research unit |
C9288
|
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: theoretical astrophysics research unit Context triple: [Theoretical Astrophysics Division, instanceOf, theoretical astrophysics research unit]
-
A.
astronomical research institute
chosen
An astronomical research institute is an organization dedicated to the systematic study of celestial objects and phenomena through observation, theory, and instrumentation development.
-
B.
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.
-
C.
astronomy department
An astronomy department is an academic unit within a college or university dedicated to teaching, research, and public outreach in the study of celestial objects and phenomena.
-
D.
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.
-
E.
research program in theoretical physics
A research program in theoretical physics is a coherent, long-term investigative framework that develops and applies mathematical models and conceptual principles to explain fundamental aspects of nature and guide future theoretical and experimental work.
- 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_69ca82894d9081908a832bfce71a4714 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:55 p.m.