Triple
T15271774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inmarsat Government |
E365036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | managed network services provider |
C36211
|
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: managed network services provider Context triple: [Inmarsat Government, instanceOf, managed network services provider]
-
A.
security service network
A security service network is an interconnected system of tools, protocols, and infrastructure designed to monitor, protect, and manage the security of digital assets and communications across distributed environments.
-
B.
network-based operating system deployment service
A network-based operating system deployment service centrally manages, configures, and automatically installs OS images over a network to multiple client machines.
-
C.
telecommunications network function
A telecommunications network function is a modular, software- or hardware-based component that performs a specific networking role—such as routing, switching, or security—within a telecom infrastructure to enable end-to-end communication services.
-
D.
security management service
A security management service is a system or organization that plans, implements, monitors, and continuously improves measures to protect an entity’s assets, information, and operations from security threats and vulnerabilities.
-
E.
managed database service
A managed database service is a cloud-based offering where the provider handles database setup, maintenance, scaling, backups, and security, allowing users to focus on using the data rather than managing the infrastructure.
- F. None of above. chosen
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.