Triple
T12515474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4880 |
E299181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | OpenPGP specification |
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: OpenPGP specification Context triple: [RFC 4880, instanceOf, OpenPGP specification]
-
A.
OpenPGP implementation
An OpenPGP implementation is a software component that provides encryption, decryption, digital signing, and key management according to the OpenPGP standard for secure communication.
-
B.
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.
-
C.
ASN.1 standard
The ASN.1 standard is a formal notation used to define, encode, transmit, and decode structured data in a platform- and language-independent way, commonly used in telecommunications and cryptographic protocols.
-
D.
revision of NIST SP 800-56C
A revision of NIST SP 800-56C is an updated version of the NIST special publication that refines and clarifies recommendations for key derivation methods in key-establishment schemes using approved cryptographic primitives.
-
E.
WHATWG specification
A WHATWG specification is a living technical standard developed by the Web Hypertext Application Technology Working Group that defines and evolves core web platform technologies such as HTML, DOM, and related APIs.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:57 p.m.