Triple
T9807833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo–Soyuz Docking Module |
E238196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft adapter |
C10281
|
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: spacecraft adapter Context triple: [Apollo–Soyuz Docking Module, instanceOf, spacecraft adapter]
-
A.
spacecraft docking system
chosen
A spacecraft docking system is a coordinated assembly of mechanical interfaces, sensors, and control software that enables two spacecraft to safely approach, align, and connect in orbit for transfer of crew, cargo, or resources.
-
B.
spacecraft berthing mechanism
A spacecraft berthing mechanism is a structural and mechanical interface system that enables two spacecraft or modules to be precisely aligned, securely joined, and later separated while maintaining required load paths and connections for power, data, and environmental control.
-
C.
spacecraft
A spacecraft is a vehicle or device designed to travel beyond Earth's atmosphere for purposes such as exploration, communication, research, or transportation.
-
D.
Spacelab subsystem
A Spacelab subsystem is a distinct functional component of the Spacelab space laboratory that performs specialized tasks—such as power, life support, data handling, or experiment support—to enable and sustain scientific operations in orbit.
-
E.
space station resupply vehicle
A space station resupply vehicle is a spacecraft designed to transport cargo, equipment, and sometimes crew to and from an orbiting space station, supporting its ongoing operations and maintenance.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.