Triple
T25499823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | short integer solution problem |
E639078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-quantum cryptography assumption |
C3162
|
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: post-quantum cryptography assumption Context triple: [short integer solution problem, instanceOf, post-quantum cryptography assumption]
-
A.
cryptographic primitive
chosen
A cryptographic primitive is a low-level, well-defined algorithm or protocol (such as a hash function, block cipher, or digital signature scheme) that serves as a basic building block for constructing more complex cryptographic systems and protocols.
-
B.
subfield of cryptography
A subfield of cryptography is a specialized area of study within cryptography that focuses on a particular set of problems, techniques, or applications, such as public-key cryptography, cryptographic protocols, or post-quantum cryptography.
-
C.
asymmetric cryptographic algorithm
An asymmetric 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, decryption, and digital signatures without sharing secret keys.
-
D.
cryptography community
A cryptography community is a group of individuals—ranging from researchers and practitioners to enthusiasts—who share, discuss, and collaborate on topics related to secure communication, encryption methods, and cryptographic protocols.
-
E.
cryptographic attack
A cryptographic attack is an attempt to defeat or weaken a cryptographic system or algorithm to gain unauthorized access to protected information or functionality.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:42 p.m.