Triple
T7918716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unity |
E183890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space station connecting module |
C10437
|
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: space station connecting module Context triple: [Unity, instanceOf, space station connecting module]
-
A.
spacecraft docking system
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
chosen
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.
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.
-
D.
orbital space station
An orbital space station is a large, habitable artificial structure that continuously orbits a celestial body, serving as a long-term platform for human presence, research, and operations in space.
-
E.
space station interface standard
A space station interface standard defines the common physical, electrical, and communication specifications that enable different spacecraft, modules, and systems to reliably connect, dock, and interoperate in orbit.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:05 p.m.