Triple
T9931143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS 1.2 PRF |
E192650
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pseudorandom function |
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 function Context triple: [TLS 1.2 PRF, instanceOf, pseudorandom function]
-
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.
block cipher mode of operation
A block cipher mode of operation is a method that specifies how to repeatedly apply a block cipher’s fixed-size transformation to larger or variably sized data to achieve secure encryption and decryption.
-
C.
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.
-
D.
pseudometric
A pseudometric is a function that assigns a nonnegative real number as a "distance" between any two points in a set, satisfying all the axioms of a metric except that distinct points are allowed to have zero distance.
-
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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:43 p.m.