Triple
T10586488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piscis Austrinus |
E249866
|
entity |
| Predicate | recognizedByIAU |
P50431
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Piscis Austrinus, recognizedByIAU, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedByIAU Context triple: [Piscis Austrinus, recognizedByIAU, yes]
-
A.
isNonOfficialIAU
Indicates that the entity’s designation or status is not officially recognized or approved by the International Astronomical Union (IAU).
-
B.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
C.
IAUNameApproval
chosen
Indicates that an official name for an astronomical object or feature has been formally approved by the International Astronomical Union (IAU).
-
D.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
-
E.
hasSIMBADIdentifier
Indicates that an astronomical object is associated with a specific identifier in the SIMBAD astronomical database.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d527698be48190a2f5e573d7cc0661 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:39 p.m.