Triple
T33829619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqr |
E867059
|
entity |
| Predicate | hasIAUCodeRole |
P135118
|
FINISHED |
| Object | constellation code |
—
|
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: constellation code | Statement: [Aqr, hasIAUCodeRole, constellation code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIAUCodeRole Context triple: [Aqr, hasIAUCodeRole, constellation code]
-
A.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
B.
belongsToIAUList
Indicates that something is included in, or officially recognized as part of, a list maintained by the International Astronomical Union (IAU).
-
C.
hasThreeLetterIAUCode
chosen
Indicates that an entity is associated with a specific three-letter code defined by the International Astronomical Union (IAU).
-
D.
hasAstronomicalCode
Indicates that an entity is associated with a specific astronomical identification code used in celestial catalogs or classification systems.
-
E.
isNonOfficialIAU
Indicates that the entity’s designation or status is not officially recognized or approved by the International Astronomical Union (IAU).
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7002143188190aed5ea871608fbc5 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.