Triple
T30369078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equihash |
E772501
|
entity |
| Predicate | miningHardwareTarget |
P169130
|
FINISHED |
| Object | general-purpose hardware |
—
|
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: general-purpose hardware | Statement: [Equihash, miningHardwareTarget, general-purpose hardware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningHardwareTarget Context triple: [Equihash, miningHardwareTarget, general-purpose hardware]
-
A.
difficultyTargetBits
Indicates the required difficulty level for a task or computation, expressed as a target number of leading zero bits that a valid solution must satisfy.
-
B.
notableMiner
Indicates that an entity is recognized as a miner of particular significance or prominence.
-
C.
hasApproximateDifficulty
Indicates that one entity is associated with another entity representing an estimated or non-exact level of difficulty.
-
D.
miningScale
Indicates the relative size or intensity of a mining operation or activity.
-
E.
summitBlockDifficulty
Indicates the level of technical challenge or effort required to reach the summit or highest point of a route or climb.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 7:59 p.m.