Triple
T32550811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-521 |
E831967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | NIST-recommended elliptic curve |
C58164
|
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: NIST-recommended elliptic curve Context triple: [P-521, instanceOf, NIST-recommended elliptic curve]
-
A.
Koblitz curve
A Koblitz curve is a special type of elliptic curve defined over a binary finite field that allows particularly efficient arithmetic using the Frobenius endomorphism, commonly used in elliptic curve cryptography.
-
B.
cryptographic parameter set family
A cryptographic parameter set family is a collection of related parameter sets, typically varying in size or security level, that define the mathematical and operational settings for a class of cryptographic algorithms.
-
C.
finite-field Diffie-Hellman group
A finite-field Diffie-Hellman group is a multiplicative group of integers modulo a prime (or prime power) used as the algebraic setting in which two parties can securely compute a shared secret via the Diffie-Hellman key exchange protocol.
-
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.
cryptographic library
A cryptographic library is a collection of software routines that implement cryptographic algorithms and protocols to provide secure encryption, decryption, hashing, key management, and related security functions for applications.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.