Triple
T10532263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-256 |
E248473
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | SHA-1 |
E437745
|
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: SHA-1 | Statement: [SHA-256, predecessor, SHA-1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SHA-1 Context triple: [SHA-256, predecessor, SHA-1]
-
A.
SHA-1
chosen
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.
-
B.
SHA-0
SHA-0 is an early, now-obsolete cryptographic hash function in the Secure Hash Algorithm family, known for its structural weaknesses and subsequent replacement by SHA-1.
-
C.
SHA-256
SHA-256 is a widely used cryptographic hash function from the SHA-2 family that produces a 256-bit hash value for securing data integrity and authentication.
-
D.
SHA-2
SHA-2 is a family of cryptographic hash functions widely used for data integrity, digital signatures, and security protocols on the internet.
-
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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a17f23081909f3372e160e21670 |
completed | April 7, 2026, 1:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90e471e9c8190b134249073b289bd |
completed | April 10, 2026, 2:50 p.m. |
Created at: April 6, 2026, 12:30 p.m.