Triple
T9029534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E216132
|
entity |
| Predicate | miningHardware |
P12755
|
FINISHED |
| Object | ASICs compatible with SHA-256 |
—
|
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: ASICs compatible with SHA-256 | Statement: [Bitcoin Cash, miningHardware, ASICs compatible with SHA-256]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miningHardware Context triple: [Bitcoin Cash, miningHardware, ASICs compatible with SHA-256]
-
A.
notableMiner
Indicates that an entity is recognized as a miner of particular significance or prominence.
-
B.
miningMethod
Indicates the technique or process used to extract minerals or resources from the earth.
-
C.
hardwareUsed
Indicates that a particular piece of hardware is utilized or employed in performing an action, process, or function involving another entity.
-
D.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
E.
hardwareUsedBy
chosen
Indicates that a piece of hardware is utilized or operated by a particular entity (such as a person, system, or organization).
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee3597c81908919cf866ae95c24 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.