Triple
T1006394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communication Theory of Secrecy Systems |
E21722
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foundational work in cryptography |
C4654
|
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: foundational work in cryptography Context triple: [Communication Theory of Secrecy Systems, instanceOf, foundational work in cryptography]
-
A.
foundational work in mathematics
Foundational work in mathematics comprises the theories, principles, and formal systems that rigorously define mathematical objects and reasoning, providing a secure logical basis for all mathematical disciplines.
-
B.
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.
-
C.
cryptography award
A cryptography award is a formal recognition given to individuals or groups for significant contributions, innovations, or achievements in the field of cryptography and information security.
-
D.
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.
-
E.
cryptanalysis unit
A cryptanalysis unit is a specialized team or organizational division dedicated to analyzing, breaking, and securing cryptographic systems and communications.
- F. None of above. chosen
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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:41 p.m.