Triple
T13684513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Defender for Cloud Apps |
E328087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud access security broker |
C26313
|
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 access security broker Context triple: [Microsoft Defender for Cloud Apps, instanceOf, cloud access security broker]
-
A.
cloud security service
chosen
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.
identity and access management service
An identity and access management service securely authenticates users and controls their permissions to access systems, applications, and data based on defined policies.
-
C.
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.
-
D.
Application security vendor
An application security vendor provides tools and services that identify, prevent, and remediate security vulnerabilities in software applications throughout their development and deployment lifecycle.
-
E.
cloud infrastructure management platform
A cloud infrastructure management platform is a centralized system that automates, orchestrates, monitors, and optimizes the provisioning, configuration, scaling, and governance of cloud resources across multiple environments and providers.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:53 p.m.