Triple
T6031324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard spectral classification |
E134309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical classification scheme |
C19795
|
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: astronomical classification scheme Context triple: [Harvard spectral classification, instanceOf, astronomical classification scheme]
-
A.
stellar classification tool
A stellar classification tool is a software system that analyzes observational data (such as spectra, colors, and luminosities) to automatically determine and label the spectral and luminosity classes of stars.
-
B.
astronomical catalogue
An astronomical catalogue is a systematically organized list of celestial objects, typically including their positions, brightness, and other observational properties for scientific reference and study.
-
C.
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.
-
D.
astronomical constellation
An astronomical constellation is a recognized area of the celestial sphere defined by the International Astronomical Union, typically associated with a traditional pattern of stars and used for mapping and identifying positions in the night sky.
-
E.
deep-sky object catalogue
A deep-sky object catalogue is a systematically organized list of non-stellar astronomical objects—such as galaxies, nebulae, and star clusters—typically including their positions, classifications, and observational properties.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:08 p.m.