Triple
T24547256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 108903 |
E607258
|
entity |
| Predicate | hasBolometricCorrection |
P156273
|
FINISHED |
| Object | significant (cool giant) |
—
|
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: significant (cool giant) | Statement: [HD 108903, hasBolometricCorrection, significant (cool giant)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBolometricCorrection Context triple: [HD 108903, hasBolometricCorrection, significant (cool giant)]
-
A.
hasCombinedApparentMagnitude
Indicates that a group of astronomical objects, when considered together, have a specific total apparent brightness as seen by an observer.
-
B.
hasAbsoluteMagnitudeBand
Indicates that an entity has an absolute magnitude value measured within a specified photometric band.
-
C.
hasPhotometry
Indicates that an entity possesses or is associated with photometric data or measurements.
-
D.
isBrightGiant
Indicates that an entity is a very luminous star of large radius and high intrinsic brightness, typically classified as a bright giant in stellar taxonomy.
-
E.
isBrightGiantIn
Indicates that an entity is a bright giant star located within a specified astronomical region or system.
- F. None of above. chosen
Provenance (4 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8caba8c819082c3bf33b6ff9cd0 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.