Triple
T36486481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Digital Processing Unit |
E898947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | onboard electronic module |
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 electronic module Context triple: [Digital Processing Unit, instanceOf, onboard electronic module]
-
A.
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.
-
B.
vehicle electronic control system
A vehicle electronic control system is an integrated hardware and software platform that monitors sensor inputs and manages actuators to optimize and coordinate a vehicle’s performance, safety, and efficiency.
-
C.
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.
-
D.
integrated avionics suite
An integrated avionics suite is a cohesive collection of aircraft electronic systems—such as navigation, communication, flight control, and monitoring—designed to work together through shared hardware, software, and data networks to enhance safety, efficiency, and pilot situational awareness.
-
E.
VMEbus board
A VMEbus board is a modular printed circuit board that plugs into a VMEbus backplane to provide processing, I/O, memory, or specialized functions within an embedded or industrial computer system.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.