Triple
T9897552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BitLocker (device encryption variant) |
E182213
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | device encryption technology |
C8833
|
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: device encryption technology Context triple: [BitLocker (device encryption variant), instanceOf, device encryption technology]
-
A.
disk encryption software
chosen
Disk encryption software is a security tool that automatically encrypts and decrypts data stored on a disk or partition, protecting its contents from unauthorized access even if the physical device is lost or stolen.
-
B.
hardware-based security technology
Hardware-based security technology refers to dedicated physical components and devices designed to protect systems and data by enforcing security functions at the hardware level, independent of or in conjunction with software controls.
-
C.
security chip
A security chip is a dedicated hardware component designed to securely store cryptographic keys and perform sensitive operations to protect devices and data from unauthorized access and tampering.
-
D.
encryption software
Encryption software is a type of application that transforms readable data into an unreadable format using cryptographic algorithms to protect its confidentiality, integrity, and, in some cases, authenticity.
-
E.
hardware security module
A hardware security module is a dedicated physical device that securely generates, stores, and manages cryptographic keys and operations to protect sensitive data and transactions from compromise.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 8:40 p.m.