Triple
T7278996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Trusted Execution Technology |
E163101
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trusted computing 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: trusted computing technology Context triple: [Intel Trusted Execution Technology, instanceOf, trusted computing 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.
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.
-
C.
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.
-
D.
chain-of-custody certification
Chain-of-custody certification is a verification process that tracks materials through each stage of production, processing, and distribution to ensure their origin, integrity, and compliance with specified standards.
-
E.
cryptographic protocol
A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:59 p.m.