Triple
T7414934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DES |
E171105
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government encryption standard |
C22172
|
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: U.S. government encryption standard Context triple: [DES, instanceOf, U.S. government encryption standard]
-
A.
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.
-
B.
Wi‑Fi security certification program
A Wi‑Fi security certification program is a formal framework that evaluates, validates, and labels wireless networks and devices against defined security standards to ensure safe and trustworthy Wi‑Fi usage.
-
C.
IEEE 802.11 security mechanism
An IEEE 802.11 security mechanism is a protocol or feature within Wi‑Fi standards designed to provide authentication, confidentiality, and integrity protection for wireless network communications.
-
D.
U.S. government trade-restriction tool
A U.S. government trade-restriction tool is a legal or regulatory mechanism—such as tariffs, sanctions, export controls, or import quotas—used to limit, condition, or prohibit cross-border commerce in order to advance national security, economic, or foreign policy objectives.
-
E.
disk encryption software
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.
- F. None of above. chosen
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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:11 p.m.