Triple
T36485190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flight Releasable Grapple Fixture |
E898916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | space hardware standard |
C10438
|
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 hardware standard Context triple: [Flight Releasable Grapple Fixture, instanceOf, space hardware standard]
-
A.
space station interface standard
chosen
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.
-
B.
International Space Station hardware
Physical components and systems that make up, support, and enable the operation of the International Space Station, including its structure, modules, instruments, and onboard equipment.
-
C.
spacecraft equipment
Spacecraft equipment comprises the specialized instruments, systems, and hardware installed on a spacecraft to support its operation, navigation, communication, scientific missions, and crew or payload needs in the space environment.
-
D.
space telescope hardware
Space telescope hardware comprises the physical components—such as mirrors, detectors, support structures, and control systems—designed to operate in space to collect and transmit astronomical data beyond Earth’s atmosphere.
-
E.
spacecraft structural component
A spacecraft structural component is a physical element that forms part of the spacecraft’s load-bearing framework, providing mechanical support, alignment, and protection for onboard systems while withstanding launch and space environment stresses.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.