Triple
T16921829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpaceWire |
E410460
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spacecraft communication standard |
C2787
|
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: spacecraft communication standard Context triple: [SpaceWire, instanceOf, spacecraft communication standard]
-
A.
space communication network
A space communication network is an interconnected system of ground stations, satellites, and relay nodes that enables the reliable transmission, routing, and reception of data across space and between space-based and terrestrial assets.
-
B.
space communication project
A space communication project is an organized effort to design, develop, and operate systems that enable reliable data and signal exchange between spacecraft, satellites, and ground stations.
-
C.
telecommunications standard
chosen
A telecommunications standard is an agreed-upon set of technical specifications and protocols that ensure compatibility, interoperability, and reliable communication across different telecom networks and devices.
-
D.
space communications program
A space communications program is an organized set of missions, technologies, and operations designed to enable reliable data and signal exchange between spacecraft, satellites, and ground systems.
-
E.
deep space communications facility
A deep space communications facility is a ground-based complex equipped with large antennas, high-power transmitters, and sensitive receivers used to send commands to and receive data from spacecraft operating far beyond Earth's orbit.
- 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.