Triple
T19291770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR 1149 |
E482459
|
entity |
| Predicate | hasHRDesignation |
P974
|
FINISHED |
| Object | HR 1149 |
—
|
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: HR 1149 | Statement: [HR 1149, hasHRDesignation, HR 1149]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HR 1149 Context triple: [HR 1149, hasHRDesignation, HR 1149]
-
A.
HR 1149
chosen
HR 1149 is a star in the Pleiades open star cluster, also known by the traditional name Taygeta.
-
B.
HR 1140
HR 1140 is a catalogued star in the constellation Perseus, listed under multiple stellar designation systems including the Henry Draper Catalogue.
-
C.
HR 1411
HR 1411 is a designated bright star in the constellation Taurus, cataloged under the Henry Draper and Harvard Revised star catalogs.
-
D.
HR 1122
HR 1122 is a catalog designation for the star HD 22951, a stellar object listed in multiple astronomical star catalogs.
-
E.
HR 1178
HR 1178 is a bright blue-white star in the Pleiades open star cluster in the constellation Taurus, traditionally known as Sterope I.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc819a7881909a7afbd06d9dd3f0 |
completed | April 20, 2026, 10:14 a.m. |
Created at: April 10, 2026, 1:31 p.m.