Triple
T36293626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Space Telescope computer |
E893299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | onboard spacecraft computer |
C7917
|
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: onboard spacecraft computer Context triple: [Hubble Space Telescope computer, instanceOf, onboard spacecraft computer]
-
A.
spacecraft onboard computer
chosen
A spacecraft onboard computer is a specialized, radiation-hardened computing system that autonomously manages spacecraft functions, navigation, communication, and data handling in the harsh environment of space.
-
B.
attitude control computer
An attitude control computer is an onboard system that calculates and commands the necessary control actions to orient and stabilize a vehicle, such as a spacecraft or aircraft, in three-dimensional space.
-
C.
S-100 bus computer
An S-100 bus computer is a microcomputer system built around the S-100 expansion bus standard, using a backplane and plug-in cards for CPU, memory, and I/O to create a modular, expandable architecture.
-
D.
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.
-
E.
modular spacecraft
A modular spacecraft is a reconfigurable space vehicle composed of interchangeable, standardized modules that can be assembled, upgraded, or replaced to support different missions and functions.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.