Triple
T2105638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3414 |
E37187
|
entity |
| Predicate | authenticationProtocol |
P35861
|
FINISHED |
| Object | HMAC-SHA-96 |
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-SHA-96 | Statement: [RFC 3414, authenticationProtocol, HMAC-SHA-96]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HMAC-SHA-96 Context triple: [RFC 3414, authenticationProtocol, HMAC-SHA-96]
-
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.
SHA
SHA is the IATA airport code for Shanghai Hongqiao International Airport, a major domestic and regional aviation hub serving Shanghai, China.
-
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.
Poly1305
Poly1305 is a high-speed message authentication code (MAC) algorithm commonly used with stream ciphers like ChaCha20 to provide data integrity and authenticity.
-
E.
MD5
MD5 is a widely known but now cryptographically broken 128-bit hash function formerly used for checksums, data integrity, and security applications.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbdc11a048190ba3bbc60f90f34e1 |
completed | March 7, 2026, 5:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae51926e4481909dd148b5cab3b6ec |
completed | March 9, 2026, 4:50 a.m. |
Created at: March 4, 2026, 7:43 p.m.