Triple
T10157927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SASL |
E233817
|
entity |
| Predicate | mechanismExample |
P92336
|
FINISHED |
| Object | DIGEST-MD5 |
E210079
|
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: DIGEST-MD5 | Statement: [SASL, mechanismExample, DIGEST-MD5]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DIGEST-MD5 Context triple: [SASL, mechanismExample, DIGEST-MD5]
-
A.
MD5
MD5 is a widely known but now cryptographically broken 128-bit hash function formerly used for checksums, data integrity, and security applications.
-
B.
CRAM-MD5
chosen
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.
-
C.
MD4
MD4 is a cryptographic hash function designed by Ronald Rivest that produces a 128-bit hash value and served as the basis for later algorithms like MD5.
-
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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d300acae608190891d8f55c3d5102b |
completed | April 6, 2026, 12:39 a.m. |
Created at: March 30, 2026, 9:09 p.m.