Triple
T21523127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gem |
E531025
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical designation code |
C20061
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: astronomical designation code Context triple: [Gem, instanceOf, astronomical designation code]
-
A.
astronomical designation element
chosen
An astronomical designation element is a component of a standardized naming or cataloging system used to uniquely identify celestial objects or phenomena.
-
B.
astronomical classification scheme
An astronomical classification scheme is a systematic method for categorizing celestial objects based on their physical properties, behaviors, and observational characteristics.
-
C.
astronomical catalogue
An astronomical catalogue is a systematically organized list of celestial objects, typically including their positions, brightness, and other observational properties for scientific reference and study.
-
D.
standardized designation
A standardized designation is an officially recognized and consistently applied label or title used to identify and categorize entities, roles, or items according to established norms or criteria.
-
E.
organizational unit of the International Astronomical Union
An organizational unit of the International Astronomical Union is a formally defined body within the IAU, such as a division, commission, or working group, responsible for coordinating and advancing specific areas of astronomical research, standards, or activities.
- F. None of above.
Provenance (1 batch)
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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:26 p.m.