Triple
T21605031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 108248 |
E533148
|
entity |
| Predicate | hasCloseSpectroscopicPair |
P144758
|
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 108248, hasCloseSpectroscopicPair, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloseSpectroscopicPair Context triple: [HD 108248, hasCloseSpectroscopicPair, true]
-
A.
hasOpticalCompanion
Indicates that one entity has another entity as an associated optical companion, typically observed as a nearby or paired object in optical wavelengths.
-
B.
hasSpectralObservation
Indicates that a spectral measurement or observation has been made of an entity, linking it to the corresponding spectral data or record.
-
C.
hasPulsarCompanion
Indicates that one astronomical object exists in a bound system with, or is accompanied by, a pulsar.
-
D.
hasSisterTelescope
Indicates that one telescope is considered a sister telescope to another, typically due to a close partnership, shared design, or coordinated observational role.
-
E.
hasSpectrograph
Indicates that one entity is equipped with or contains a spectrograph instrument.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e4a8088190bf51ab2af2369762 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:33 p.m.