Triple
T26409132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GHASH |
E663911
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | message authentication primitive |
C9659
|
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: message authentication primitive Context triple: [GHASH, instanceOf, message authentication primitive]
-
A.
message authentication code
chosen
A message authentication code (MAC) is a short piece of information generated from a message and a secret key that verifies both the message’s integrity and the authenticity of its sender.
-
B.
cryptographic protocol message
A cryptographic protocol message is a structured unit of data exchanged between parties in a cryptographic protocol, containing information such as identifiers, nonces, keys, and signatures to achieve security goals like confidentiality, integrity, and authentication.
-
C.
authentication message
An authentication message is a structured communication containing credentials or security tokens used to verify the identity of a user, device, or system before granting access to protected resources.
-
D.
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.
-
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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:37 p.m.