Triple
T32498515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSS (Probabilistic Signature Scheme) |
E830589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | probabilistic signature scheme |
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: probabilistic signature scheme Context triple: [PSS (Probabilistic Signature Scheme), instanceOf, probabilistic signature scheme]
-
A.
cryptographic scheme family
A cryptographic scheme family is a parameterized collection of related cryptographic schemes (e.g., keyed by security parameter or algorithm variant) that share a common structure and security goals while differing in specific instantiations or parameters.
-
B.
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.
-
C.
cryptographic protocol component
A cryptographic protocol component is a modular element—such as a key exchange, authentication step, or encryption mechanism—that participates in a larger protocol to provide specific security properties like confidentiality, integrity, or authenticity.
-
D.
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.
-
E.
signature
A signature is a unique personal mark, written or digital, that identifies and authenticates the approval, authorship, or consent of an individual or entity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.