Triple
T29638225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augmented Target Docking Adapter |
E755783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gemini program hardware |
C22460
|
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: Gemini program hardware Context triple: [Augmented Target Docking Adapter, instanceOf, Gemini program hardware]
-
A.
Gemini program management structure
The Gemini program management structure is an organized framework of roles, responsibilities, and processes designed to plan, coordinate, and oversee all phases of the Gemini initiative to ensure its objectives are delivered efficiently and effectively.
-
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
chosen
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.
Saturn V mobile launcher
The Saturn V mobile launcher was a massive, self-contained launch platform and service structure that transported, supported, and provided umbilical connections to the Saturn V rocket from assembly to liftoff.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
Created at: April 28, 2026, 6:45 p.m.