Triple
T32370413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Association of Lunar and Planetary Observers |
E827117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | astronomical organization |
C50199
|
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 organization Context triple: [Association of Lunar and Planetary Observers, instanceOf, astronomical organization]
-
A.
astronomical society
chosen
An astronomical society is an organized group dedicated to the study, observation, and promotion of astronomy among its members and the public.
-
B.
astronomical advisory committee
An astronomical advisory committee is a group of experts convened to provide informed guidance, recommendations, and oversight on policies, priorities, and strategies related to astronomical research and space science activities.
-
C.
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.
-
D.
representative body of astronomers
A representative body of astronomers is an organized group or council elected or appointed to advocate for, coordinate, and make collective decisions on behalf of the astronomical community.
-
E.
astronomical asterism group
An astronomical asterism group is a recognizable pattern or grouping of stars in the sky that forms an informal visual figure, distinct from officially defined constellations.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:50 a.m.