Triple
T26986915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 22049 |
E679757
|
entity |
| Predicate | hasChromosphericActivity |
P29861
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [HD 22049, hasChromosphericActivity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChromosphericActivity Context triple: [HD 22049, hasChromosphericActivity, true]
-
A.
chromosphericActivity
chosen
Indicates the level or presence of energetic phenomena and emissions occurring in the chromosphere of a star, typically reflecting its magnetic activity.
-
B.
hasRadialPulsations
Indicates that an entity exhibits rhythmic expansions and contractions radiating outward from a central point.
-
C.
isSunLike
Indicates that one celestial object shares key physical and behavioral characteristics with the Sun, such as mass, temperature, luminosity, and spectral type.
-
D.
hasAccretionActivity
Indicates that an object is currently undergoing or exhibiting accretion, i.e., the process of accumulating mass from surrounding material.
-
E.
hasStellarSpectrum
Indicates that an astronomical object exhibits a particular stellar spectrum characterizing its emitted light across wavelengths.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 6:49 a.m.