Triple
T36096390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurs |
E1044073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | automated rendezvous system |
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: automated rendezvous system Context triple: [Kurs, instanceOf, automated rendezvous system]
-
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.
autonomous navigation system
An autonomous navigation system is a self-directed control framework that enables vehicles or robots to perceive their environment, plan routes, and move safely to a destination without human intervention.
-
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.
joint planning and execution system
A joint planning and execution system is an integrated framework that enables multiple agents or stakeholders to collaboratively create, coordinate, and carry out shared plans toward common goals in dynamic environments.
-
E.
X-ray pulsar navigation experiment
An X-ray pulsar navigation experiment is a test of spacecraft guidance technology that uses the regular X-ray pulses from distant neutron stars as natural beacons to autonomously determine a vehicle’s position and velocity 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.