Triple
T15271773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inmarsat Government |
E365036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | satellite communications provider |
C25836
|
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 communications provider Context triple: [Inmarsat Government, instanceOf, satellite communications provider]
-
A.
satellite operator
chosen
A satellite operator is an entity responsible for controlling, monitoring, and managing satellites and their payloads to deliver space-based services such as communications, navigation, or Earth observation.
-
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.
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.
-
D.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
-
E.
mobile satellite service system
A mobile satellite service system is a communication network that uses satellites to provide voice, data, and messaging connectivity to mobile users over wide geographic areas, including remote and underserved regions.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:14 a.m.