Triple
T37100563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLOUDY |
E918689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | photoionization code |
C63236
|
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: photoionization code Context triple: [CLOUDY, instanceOf, photoionization code]
-
A.
plane-wave pseudopotential code
A plane-wave pseudopotential code is a computational program that uses plane-wave basis sets and pseudopotentials to efficiently solve the electronic structure of materials within quantum mechanical frameworks such as density functional theory.
-
B.
plane-wave DFT code
A plane-wave DFT code is a computational program that solves the Kohn–Sham equations of density functional theory using plane waves as a basis set, typically combined with pseudopotentials, to calculate the electronic structure and related properties of periodic systems.
-
C.
high-energy astrophysics software
High-energy astrophysics software comprises specialized tools and frameworks for processing, analyzing, and modeling data from high-energy phenomena such as X-ray and gamma-ray sources in the universe.
-
D.
stellar evolution code
A stellar evolution code is a computational tool that simulates the physical processes governing a star’s life cycle, from formation to end stages, by numerically solving the equations of stellar structure and evolution.
-
E.
X-ray astronomy software
X-ray astronomy software is specialized computational tools and pipelines used to process, analyze, and visualize X-ray data from space- and ground-based observatories to study high-energy astrophysical phenomena.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.