Triple
T9931147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS 1.2 PRF |
E192650
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | HMAC |
E37198
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: HMAC | Statement: [TLS 1.2 PRF, basedOn, HMAC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HMAC Context triple: [TLS 1.2 PRF, basedOn, HMAC]
-
A.
HMAC
chosen
HMAC (Hash-based Message Authentication Code) is a cryptographic construction that combines a secret key with a hash function to provide data integrity and authentication.
-
B.
CBC-MAC
CBC-MAC (Cipher Block Chaining Message Authentication Code) is a cryptographic technique that uses a block cipher in CBC mode to generate a fixed-size tag for ensuring data integrity and authenticity.
-
C.
CRAM-MD5
CRAM-MD5 is a challenge–response authentication mechanism that uses MD5 hashing to securely verify a user's identity without transmitting their password in plaintext.
-
D.
Hash
"Hash" is a darkly comic novel by Swedish author Torgny Lindgren that explores memory, identity, and rural life through the story of two men obsessively disputing who makes the better potato hash.
-
E.
SHA-1
SHA-1 is a now-legacy 160-bit cryptographic hash function once widely used for data integrity and digital signatures but today considered insecure due to practical collision attacks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d228cab0fc81908ff5fad6916c1bab |
completed | April 5, 2026, 9:18 a.m. |
Created at: March 30, 2026, 8:43 p.m.