Triple
T29937482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epsilon Centauri |
E760408
|
entity |
| Predicate | hasColorIndex_UminusB |
P63031
|
FINISHED |
| Object | ~−0.95 |
—
|
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.95 | Statement: [Epsilon Centauri, hasColorIndex_UminusB, ~−0.95]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorIndex_UminusB Context triple: [Epsilon Centauri, hasColorIndex_UminusB, ~−0.95]
-
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.
isBicolor
Indicates that something consists of or displays two distinct colors.
-
E.
isColorCharged
Indicates that an entity possesses color charge, meaning it carries the type of charge associated with the strong nuclear interaction in quantum chromodynamics.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: April 29, 2026, 6:21 p.m.