Triple
T20679801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collinder 140 |
E508259
|
entity |
| Predicate | hasColorExcessEBV |
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: [Collinder 140, hasColorExcessEBV, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColorExcessEBV Context triple: [Collinder 140, hasColorExcessEBV, low]
-
A.
reddening_E_BV
chosen
Indicates the color excess E(B−V), quantifying the amount of reddening (dust-induced color change) between two photometric bands.
-
B.
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.
-
C.
hasDustExtinction
Indicates that an entity exhibits or is subject to attenuation of light due to the presence of intervening dust.
-
D.
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.
-
E.
hasAlbedo
Indicates that an entity possesses a specific reflectivity or albedo value, describing how much incoming light it reflects.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea516b88190b3e90d03fa981a44 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.