Triple
T18775666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 168454 |
E459126
|
entity |
| Predicate | hasColorIndexUminusB |
P63031
|
FINISHED |
| Object | −0.10 |
—
|
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.10 | Statement: [HD 168454, hasColorIndexUminusB, −0.10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorIndexUminusB Context triple: [HD 168454, hasColorIndexUminusB, −0.10]
-
A.
hasUminusBColorIndex
chosen
Indicates that there is a specified U−B color index value characterizing the color difference between two photometric bands in a subject.
-
B.
hasColorIndexB-R
Indicates that one entity has a specified B–R color index value, representing the difference between its blue and red magnitudes.
-
C.
colorIndexB−V
Indicates the difference between an object's blue (B) and visual (V) magnitudes, representing its color and thus its temperature or spectral characteristics.
-
D.
hasComplementaryColor
Indicates that one color is the complementary (i.e., opposite on the color wheel, providing maximum contrast) counterpart of another color.
-
E.
isBicolor
Indicates that something consists of or displays two distinct colors.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933ad4288190b17e5fad57d8417d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.