Triple
T20512691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yao’s pseudorandom generator construction |
E503603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pseudorandom generator construction |
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: pseudorandom generator construction Context triple: [Yao’s pseudorandom generator construction, instanceOf, pseudorandom generator construction]
-
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.
stream cipher
A stream cipher is an encryption method that converts plaintext to ciphertext by combining it with a pseudorandom keystream, processing data one bit or byte at a time.
-
C.
stream cipher evaluation initiative
A stream cipher evaluation initiative is a coordinated effort to systematically analyze, compare, and validate the security, performance, and practicality of stream cipher algorithms against defined criteria and real-world use cases.
-
D.
cryptographic protocol framework
A cryptographic protocol framework is a structured set of tools, abstractions, and rules that enables the design, specification, analysis, and implementation of secure communication protocols.
-
E.
cryptographic data structure
A cryptographic data structure is a data organization that uses cryptographic primitives to ensure properties like integrity, authenticity, privacy, or verifiability of the stored or processed information.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:36 a.m.