Triple
T1613512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Core |
E34661
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bitcoin reference implementation |
C1444
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Bitcoin reference implementation Context triple: [Bitcoin Core, instanceOf, Bitcoin reference implementation]
-
A.
peer-to-peer electronic cash system
A peer-to-peer electronic cash system is a decentralized digital payment network that allows users to send value directly to one another over the internet without relying on trusted intermediaries like banks or payment processors.
-
B.
reference implementation
chosen
A reference implementation is a canonical, typically straightforward version of a system or specification created to demonstrate correct behavior and serve as a standard for other implementations.
-
C.
miner
A miner is a worker who extracts valuable minerals, ores, or other geological materials from the earth, typically operating in underground or surface mines using specialized tools and machinery.
-
D.
cryptographic protocol framework
A cryptographic protocol framework is a structured set of tools, abstractions, and rules that enables the design, specification, analysis, and implementation of secure communication protocols.
-
E.
cryptocurrency
A cryptocurrency is a digital or virtual currency that uses cryptography and decentralized blockchain technology to secure transactions, control the creation of new units, and verify the transfer of assets without relying on a central authority.
- F. None of above.
Provenance (1 batch)
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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.