Triple
T14388802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qualcomm Secure Execution Environment |
E356789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hardware-backed security technology |
C13231
|
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: hardware-backed security technology Context triple: [Qualcomm Secure Execution Environment, instanceOf, hardware-backed security technology]
-
A.
hardware-based security technology
chosen
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.
-
B.
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.
-
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.
hardware-assisted virtualization technology
Hardware-assisted virtualization technology is a set of CPU and chipset features that enable virtual machines to run more efficiently and securely by offloading key virtualization tasks from software to the hardware layer.
-
E.
security mechanism
A security mechanism is a method, process, or tool designed to protect systems, data, or communications from unauthorized access, misuse, or harm.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:16 a.m.