Triple
T6094967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saiph |
E135853
|
entity |
| Predicate | hasStellarSpectrum |
P68087
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Saiph, hasStellarSpectrum, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStellarSpectrum Context triple: [Saiph, hasStellarSpectrum, yes]
-
A.
spectralClass
Indicates the classification of an astronomical object based on the characteristics of its spectrum, such as temperature and spectral features.
-
B.
hasStellarStream
Indicates that one astronomical object possesses or is associated with a coherent flow of stars, known as a stellar stream, typically resulting from tidal interactions or disruption.
-
C.
dominantSpectralType
Indicates the primary or most prevalent spectral type characterizing the electromagnetic emission of an object or region.
-
D.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
-
E.
containsStellarPopulation
Indicates that one astronomical object includes or encompasses a group of stars as part of its stellar content.
- F. None of above. chosen
Provenance (4 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05a963bac8190bc0c33fef187875c |
completed | March 22, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:12 p.m.