Triple
T32542443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat–Shamir heuristic |
E831747
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cryptographic heuristic |
C59328
|
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: cryptographic heuristic Context triple: [Fiat–Shamir heuristic, instanceOf, cryptographic heuristic]
-
A.
cryptographic primitive
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.
cryptographic paradigm
chosen
A cryptographic paradigm is a high-level conceptual framework that defines how cryptographic primitives are combined and used to achieve specific security goals in protocols and systems.
-
C.
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.
-
D.
cryptographic test
A cryptographic test is a systematic procedure used to evaluate the correctness, strength, and implementation security of cryptographic algorithms, protocols, or systems under defined conditions.
-
E.
cryptographic protocol
A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.