Triple
T22999618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acubens |
E572598
|
entity |
| Predicate | isIAUApprovedNameFor |
P50431
|
FINISHED |
| Object | Alpha Cancri |
—
|
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: Alpha Cancri | Statement: [Acubens, isIAUApprovedNameFor, Alpha Cancri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIAUApprovedNameFor Context triple: [Acubens, isIAUApprovedNameFor, Alpha Cancri]
-
A.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
B.
IAUNameApproval
chosen
Indicates that an official name for an astronomical object or feature has been formally approved by the International Astronomical Union (IAU).
-
C.
isNonOfficialIAU
Indicates that the entity’s designation or status is not officially recognized or approved by the International Astronomical Union (IAU).
-
D.
isAcceptedName
Indicates that a given name is the currently recognized, valid, and officially accepted designation for an entity within a particular naming or classification system.
-
E.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.