Triple
T4570092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDA-1 |
E123008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | International Docking Adapter unit |
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: International Docking Adapter unit Context triple: [IDA-1, instanceOf, International Docking Adapter unit]
-
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.
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.
-
C.
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.
-
D.
ISS external payload
An ISS external payload is a scientific or technological instrument package mounted on the outside of the International Space Station to conduct experiments, observations, or demonstrations in the space environment.
-
E.
crewed space station
A crewed space station is a permanently or semi-permanently inhabited orbital facility that supports human life and scientific, technological, or operational activities in space.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:10 p.m.