Triple
T23188781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 2632 |
E579670
|
entity |
| Predicate | hasColorExcess_E_BV |
P56977
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [NGC 2632, hasColorExcess_E_BV, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorExcess_E_BV Context triple: [NGC 2632, hasColorExcess_E_BV, low]
-
A.
hasColorExcess
Indicates that an entity exhibits a measured amount of color excess, typically representing the difference between its observed color and its intrinsic or expected color.
-
B.
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.
-
C.
hasColorIndexB-R
Indicates that one entity has a specified B–R color index value, representing the difference between its blue and red magnitudes.
-
D.
reddening_E_BV
chosen
Indicates the color excess E(B−V), quantifying the amount of reddening (dust-induced color change) between two photometric bands.
-
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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd592248190a7e705c554885cd1 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.