Triple
T23744267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 80632 |
E586768
|
entity |
| Predicate | hasSAOCatalogueNumber |
P24825
|
FINISHED |
| Object | 80632 |
—
|
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: 80632 | Statement: [SAO 80632, hasSAOCatalogueNumber, 80632]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSAOCatalogueNumber Context triple: [SAO 80632, hasSAOCatalogueNumber, 80632]
-
A.
catalogNumberDDO
Indicates the identifier or catalog number assigned to an item within the DDO cataloging or documentation system.
-
B.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
C.
alternativeCatalogNumber
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
D.
saoNumber
chosen
Indicates a relationship where an entity is identified or referenced by its SAO (Smithsonian Astrophysical Observatory) catalog number.
-
E.
hasStarCatalogIdentifier
Indicates that an astronomical object is associated with a specific identifier assigned to it in a star catalog.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbcc4f88190a00fceeafbfb5cfd |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:12 p.m.