Triple
T23009707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nova Cygni 1886 |
E572872
|
entity |
| Predicate | spectralTypeAtMaximum |
P52318
|
FINISHED |
| Object | A-type |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: A-type | Statement: [Nova Cygni 1886, spectralTypeAtMaximum, A-type]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spectralTypeAtMaximum Context triple: [Nova Cygni 1886, spectralTypeAtMaximum, A-type]
-
A.
spectralTypeACharacteristic
Indicates that an entity has a characteristic or property associated with spectral type A (e.g., typical of A-type spectra).
-
B.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
-
C.
spectralClass
chosen
Indicates the classification of an astronomical object based on the characteristics of its spectrum, such as temperature and spectral features.
-
D.
spectralTypeFCharacteristic
Indicates that something exhibits characteristics typical of F-type spectral classification, such as those associated with F-type stars in astrophysics.
-
E.
spectralTypeOfIonizingStar
Indicates the spectral classification assigned to the star that provides the ionizing radiation.
- F. None of above.
Provenance (3 batches)
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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.