Triple
T35406197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedRAMP Marketplace package |
E1023368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud service security package |
C6083
|
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: cloud service security package Context triple: [FedRAMP Marketplace package, instanceOf, cloud service security package]
-
A.
cloud security service
A cloud security service is a managed solution that protects cloud-based infrastructure, applications, and data through continuous monitoring, threat detection, access control, and compliance enforcement.
-
B.
cybersecurity service
A cybersecurity service is a professional offering that protects digital systems, networks, and data from unauthorized access, attacks, and other security threats through monitoring, prevention, detection, and response measures.
-
C.
cloud service
chosen
A cloud service is an on-demand, internet-delivered computing resource—such as storage, processing power, or applications—managed by a provider and accessed remotely by users.
-
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.
cloud-native application protection platform
A cloud-native application protection platform is an integrated security solution that safeguards cloud-native applications across the entire lifecycle—covering development, deployment, and runtime—by unifying vulnerability management, configuration security, runtime threat detection, and compliance for containers, Kubernetes, serverless, and related cloud services.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.