Triple
T22766307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 landing site |
E563136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographical feature on the Moon |
C12603
|
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: geographical feature on the Moon Context triple: [Apollo 11 landing site, instanceOf, geographical feature on the Moon]
-
A.
lunar surface feature
chosen
A lunar surface feature is any distinct physical formation or characteristic on the Moon’s exterior, such as craters, maria, mountains, rilles, or valleys, identifiable by its shape, size, and location.
-
B.
surface feature on a natural satellite
A surface feature on a natural satellite is any distinct physical formation or structure—such as craters, mountains, valleys, or plains—found on the exterior of a moon or similar orbiting body.
-
C.
lunar-like crater on Phobos
A lunar-like crater on Phobos is an impact-formed, bowl-shaped depression on the Martian moon whose morphology—such as raised rims, ejecta blankets, and sometimes central peaks—closely resembles typical craters found on Earth’s Moon.
-
D.
surface feature of Mars
A surface feature of Mars is any distinct physical formation or characteristic on the Martian terrain, such as craters, valleys, volcanoes, dunes, or polar ice caps, that can be observed and studied to understand the planet’s geology and history.
-
E.
surface feature on Phobos
A surface feature on Phobos is any distinct geological or morphological structure found on the Martian moon’s exterior, such as craters, grooves, ridges, or boulders.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:26 p.m.