Triple
T30369085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equihash |
E772501
|
entity |
| Predicate | hashFunctionInput |
P8884
|
FINISHED |
| Object | block header data |
—
|
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: block header data | Statement: [Equihash, hashFunctionInput, block header data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashFunctionInput Context triple: [Equihash, hashFunctionInput, block header data]
-
A.
hashFunction
chosen
Indicates a relationship where an input value is transformed into a fixed-size output (hash) according to a specific deterministic hashing algorithm.
-
B.
hashFamily
Indicates that a hash function belongs to, or is a member of, a particular family of related hash functions.
-
C.
roundFunctionInput
Indicates that a given value is used as an input to a rounding function in a computation or process.
-
D.
hashComponent
Indicates that one entity is a constituent part used in computing the hash value of another entity.
-
E.
cryptFunction
Indicates a function or method that performs cryptographic processing, such as encrypting, decrypting, or otherwise transforming data using a cryptographic algorithm.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682825f408190b6510f20015c4e52 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.