Triple
T3513989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Satellite Control Network |
E74262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite ground control network |
C7369
|
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: satellite ground control network Context triple: [Air Force Satellite Control Network, instanceOf, satellite ground control network]
-
A.
space communication network
chosen
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.
ground segment equipment
Ground segment equipment comprises the terrestrial hardware and software systems that support, control, communicate with, and process data from space-based assets such as satellites.
-
C.
GNSS reference network
A GNSS reference network is a coordinated system of continuously operating GNSS stations that provide precise, stable positioning and timing references for surveying, navigation, and geospatial applications.
-
D.
geostationary communications satellite
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.
-
E.
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.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:19 p.m.