Triple
T33839754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 subsatellite |
E867326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apollo program hardware |
C28990
|
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: Apollo program hardware Context triple: [Apollo 15 subsatellite, instanceOf, Apollo program hardware]
-
A.
Apollo spacecraft variant
An Apollo spacecraft variant is a specific configuration or modification of the Apollo command and service modules, and sometimes the lunar module, tailored to different mission profiles, technological updates, or experimental objectives within the Apollo program.
-
B.
Apollo Lunar Module
The Apollo Lunar Module was a two-stage, crewed spacecraft designed exclusively for lunar orbit operations and surface landings during NASA's Apollo missions.
-
C.
NASA ground support equipment
NASA ground support equipment comprises the specialized tools, structures, and systems used on the ground to assemble, test, transport, service, and launch spacecraft and launch vehicles safely and reliably.
-
D.
Space Shuttle subsystem
A Space Shuttle subsystem is a distinct functional component or collection of components within the Space Shuttle that performs a specific role—such as propulsion, life support, guidance, or power management—to enable safe and effective mission operations.
-
E.
lunar orbiter mission
chosen
A lunar orbiter mission is a spaceflight operation in which a spacecraft is placed into orbit around the Moon to conduct sustained observations, measurements, and communications for scientific, exploration, or operational objectives.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.