Triple
T29768348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Muscae |
E753976
|
entity |
| Predicate | henryDraperDesignation |
P69913
|
FINISHED |
| Object | HD 109668 |
—
|
NE NERFINISHED |
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: HD 109668 | Statement: [Alpha Muscae, henryDraperDesignation, HD 109668]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: henryDraperDesignation Context triple: [Alpha Muscae, henryDraperDesignation, HD 109668]
-
A.
hasHenryDraperNumber
chosen
Indicates that an astronomical object is identified by a specific Henry Draper Catalogue number.
-
B.
bayerDesignation
Indicates the assignment of a star’s Bayer designation, linking a star to its specific Greek-letter-plus-constellation label used in astronomy.
-
C.
flamsteedDesignation
Indicates the Flamsteed catalog number assigned to a star within its constellation, expressing that specific designation relationship.
-
D.
hasNumberOfBayerFlamsteedStars
Indicates the quantity of stars in a constellation that have either Bayer or Flamsteed designations.
-
E.
hasBayerFlamsteedDesignation
Indicates that an astronomical object is associated with a specific Bayer-Flamsteed star designation in a catalog.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:40 p.m.