Triple
T9931537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKCS #8 |
E192658
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | PKCS standard |
C9660
|
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: PKCS standard Context triple: [PKCS #8, instanceOf, PKCS standard]
-
A.
public-key cryptography standard
chosen
A public-key cryptography standard is a formally defined specification that governs how asymmetric key pairs are generated, distributed, and used to securely encrypt, decrypt, sign, and verify digital data.
-
B.
smart card standard
A smart card standard is a formal specification that defines the physical, electrical, communication, and data structures required to ensure interoperability and security for smart card technologies across different systems and devices.
-
C.
U.S. government encryption standard
A U.S. government encryption standard is an officially approved cryptographic algorithm or protocol, such as AES, mandated or recommended by federal authorities to protect sensitive government and public-sector information.
-
D.
public key infrastructure component
A public key infrastructure component is an element (such as a certificate authority, registration authority, or repository) that issues, manages, stores, and validates digital certificates and cryptographic keys to enable secure, trusted communications.
-
E.
public-key cryptographic algorithm
A public-key cryptographic algorithm is a method that uses a mathematically related pair of keys—one public and one private—to enable secure operations such as encryption, digital signatures, and key exchange over untrusted networks.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:43 p.m.