Triple
T23188731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Canis Minoris |
E579669
|
entity |
| Predicate | hasWDSDesignation |
P151291
|
FINISHED |
| Object | 07271+0817 |
—
|
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: 07271+0817 | Statement: [Beta Canis Minoris, hasWDSDesignation, 07271+0817]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWDSDesignation Context triple: [Beta Canis Minoris, hasWDSDesignation, 07271+0817]
-
A.
hasDiscoveryDesignation
Indicates that an entity has been assigned a specific designation or label associated with its discovery.
-
B.
hasBDDesignation
Indicates that an entity has been assigned a specific BD (Business Development or similar domain-specific) designation or classification.
-
C.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
D.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
E.
hasESODesignation
Indicates that an entity is assigned a specific designation or identifier by the European Southern Observatory (ESO).
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd592248190a7e705c554885cd1 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:05 p.m.