Triple
T13612122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Purview Data Loss Prevention |
E325216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data loss prevention solution |
C31230
|
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: data loss prevention solution Context triple: [Microsoft Purview Data Loss Prevention, instanceOf, data loss prevention solution]
-
A.
data protection solution
chosen
A data protection solution is a system or set of tools and practices designed to safeguard data from loss, corruption, unauthorized access, and misuse throughout its lifecycle.
-
B.
disaster recovery solution
A disaster recovery solution is a comprehensive system of tools, processes, and policies designed to quickly restore critical IT services and data after disruptive events, minimizing downtime and business impact.
-
C.
Microsoft Defender for Office 365 capability
A Microsoft Defender for Office 365 capability represents a specific security function or feature that protects email and collaboration workloads from threats such as phishing, malware, and business email compromise.
-
D.
information governance tool
An information governance tool is a system that helps organizations define, enforce, and monitor policies for managing data throughout its lifecycle to ensure compliance, security, quality, and proper usage.
-
E.
data lake service
A data lake service is a scalable, centralized repository that stores vast amounts of raw, structured, and unstructured data and provides tools for ingestion, management, and analytics.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:50 p.m.