Triple
T29468378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Catalogue of Lunar Nomenclature |
E747443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical nomenclature standard |
C33524
|
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 nomenclature standard Context triple: [NASA Catalogue of Lunar Nomenclature, instanceOf, astronomical nomenclature standard]
-
A.
astronomical designation element
An astronomical designation element is a component of a standardized naming or cataloging system used to uniquely identify celestial objects or phenomena.
-
B.
astrometric standard
An astrometric standard is a celestial object with precisely known position and motion used as a reference to calibrate and validate astrometric measurements.
-
C.
lunar nomenclature system
chosen
A lunar nomenclature system is a structured scheme for naming and categorizing features on the Moon’s surface, such as craters, maria, and mountains, according to standardized rules and conventions.
-
D.
astronomical reference parameter
An astronomical reference parameter is a standardized value or constant used to define, calibrate, or relate measurements in astronomy, such as positions, motions, or physical properties of celestial objects, within a chosen reference frame or system.
-
E.
astronomical classification scheme
An astronomical classification scheme is a systematic method for categorizing celestial objects based on their physical properties, behaviors, and observational characteristics.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 3:55 p.m.