Triple
T26726879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HS-376 |
E673858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | communications satellite bus |
C12006
|
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: communications satellite bus Context triple: [HS-376, instanceOf, communications satellite bus]
-
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.
geostationary communications satellite
chosen
A geostationary communications satellite is a spacecraft positioned in an equatorial orbit that matches Earth's rotation, remaining fixed over one longitude to relay telecommunications signals between ground stations.
-
C.
satellite system
A satellite system is an integrated network of orbiting spacecraft, ground stations, and communication links designed to perform functions such as communication, navigation, Earth observation, or scientific research.
-
D.
military satellite
A military satellite is an artificial satellite deployed and operated by armed forces to support defense-related functions such as reconnaissance, communications, navigation, early warning, and targeting.
-
E.
satellite platform derivative
A satellite platform derivative is a modified version of an existing satellite bus or platform, adapted with changes in structure, subsystems, or payload interfaces to meet new mission requirements while leveraging the original design.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:43 a.m.