Triple
T11871377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmony nadir port |
E282414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft berthing and docking location |
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: spacecraft berthing and docking location Context triple: [Harmony nadir port, instanceOf, spacecraft berthing and docking location]
-
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.
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.
-
D.
NASA spaceport
A NASA spaceport is a specialized aerospace facility where NASA prepares, launches, and sometimes recovers spacecraft and launch vehicles for missions into space.
-
E.
spaceport facility
A spaceport facility is a complex of specialized infrastructure and services designed to support the launch, landing, maintenance, and logistical operations of spacecraft and their crews.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:43 p.m.