Triple
T7899336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P2PKH |
E183408
|
entity |
| Predicate | hashConstruction |
P38699
|
FINISHED |
| Object | HASH160 (RIPEMD-160(SHA-256(pubkey))) |
—
|
LITERAL 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: HASH160 (RIPEMD-160(SHA-256(pubkey))) | Statement: [P2PKH, hashConstruction, HASH160 (RIPEMD-160(SHA-256(pubkey)))]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashConstruction Context triple: [P2PKH, hashConstruction, HASH160 (RIPEMD-160(SHA-256(pubkey)))]
-
A.
Merkle–Damgård strengthening
Indicates that a hash function construction applies Merkle–Damgård strengthening, meaning the message is padded with its length (and possibly other structured padding) before processing to help ensure collision resistance and proper security properties.
-
B.
hashFunction
Indicates a relationship where an input value is transformed into a fixed-size output (hash) according to a specific deterministic hashing algorithm.
-
C.
hasConstruction
chosen
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
D.
checksum
Indicates that a value has been computed from data to verify its integrity or detect errors in transmission or storage.
-
E.
cryptDesigner
Indicates that an entity is the designer or creator responsible for planning or conceiving a particular crypt.
- F. None of above.
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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a3dc2208190a6fea93b60b8daca |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.