Triple
T19401730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Back |
E485340
|
entity |
| Predicate | knownFor |
P22
|
FINISHED |
| Object | Hashcash |
—
|
NE NERFINISHED |
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: Hashcash | Statement: [Adam Back, knownFor, Hashcash]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hashcash Context triple: [Adam Back, knownFor, Hashcash]
-
A.
Equihash
Equihash is a memory-hard, proof-of-work hashing algorithm designed to be ASIC-resistant and used in cryptocurrencies such as Zcash.
-
B.
Proof of Work
chosen
Proof of Work is a consensus mechanism in blockchain networks where participants solve computationally intensive puzzles to validate transactions and secure the ledger.
-
C.
Merkle
Merkle is a surname most prominently associated with Ralph Merkle, a pioneering computer scientist and cryptographer known for his foundational work in public-key cryptography and Merkle trees.
-
D.
DigiCash
DigiCash was an early digital currency company founded by cryptographer David Chaum that pioneered privacy-preserving electronic cash systems in the 1990s.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62577454c81909d5bcd07e99b27e4 |
completed | April 20, 2026, 1:09 p.m. |
Created at: April 10, 2026, 1:36 p.m.