Triple
T10451128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iridium satellite system |
E246425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite communication system |
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 communication system Context triple: [Iridium satellite system, instanceOf, satellite communication system]
-
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.
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.
-
C.
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.
-
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.
satellite program
A satellite program is an organized initiative that designs, builds, launches, and operates satellites to achieve specific objectives such as communication, Earth observation, navigation, or scientific research.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:17 p.m.