Triple
T4619051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaus Australis |
E100934
|
entity |
| Predicate | hasColorIndexBminusV |
P24818
|
FINISHED |
| Object | −0.03 |
—
|
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: −0.03 | Statement: [Kaus Australis, hasColorIndexBminusV, −0.03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorIndexBminusV Context triple: [Kaus Australis, hasColorIndexBminusV, −0.03]
-
A.
colorIndexB−V
chosen
Indicates the difference between an object's blue (B) and visual (V) magnitudes, representing its color and thus its temperature or spectral characteristics.
-
B.
apparentMagnitudeV
Indicates the visual brightness of an astronomical object as seen from Earth, measured in the V (visual) band of the electromagnetic spectrum.
-
C.
bayerDesignation
Indicates the assignment of a star’s Bayer designation, linking a star to its specific Greek-letter-plus-constellation label used in astronomy.
-
D.
hasColorRange
Indicates that an entity possesses or is associated with a specific span or set of colors, rather than a single discrete color.
-
E.
hasRGB
Indicates that an entity possesses or is associated with a specific RGB (red, green, blue) color value.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.