Triple
T16921831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceWire |
E410460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | onboard data-handling network |
C14212
|
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 data-handling network Context triple: [SpaceWire, instanceOf, onboard data-handling network]
-
A.
avionics data bus
chosen
An avionics data bus is a communication system within an aircraft that transfers digital data between avionics components, such as sensors, flight computers, and control systems, to ensure coordinated and reliable operation.
-
B.
data center network
A data center network is a specialized, high-performance communication infrastructure that interconnects servers, storage systems, and networking devices within and between data centers to enable efficient, reliable data exchange and application delivery.
-
C.
data processing capability
Data processing capability is the capacity of a system to efficiently collect, transform, analyze, and output data to support specific tasks or decision-making processes.
-
D.
satellite-based data collection system
A satellite-based data collection system is an integrated network of orbiting satellites, ground stations, and processing infrastructure that remotely senses, gathers, transmits, and analyzes data from Earth or space environments for monitoring, communication, and decision-making purposes.
-
E.
spacecraft onboard computer
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.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.