Triple
T7899212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bitcoin-cli |
E183406
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bitcoin RPC client |
C23137
|
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 RPC client Context triple: [bitcoin-cli, instanceOf, Bitcoin RPC client]
-
A.
Bitcoin block
A Bitcoin block is a data structure in the blockchain that groups a set of validated transactions, references the previous block via a cryptographic hash, and includes a proof-of-work to secure and order transactions in the network.
-
B.
public blockchain
A public blockchain is a decentralized, permissionless distributed ledger where anyone can join the network, validate transactions, and access the full transaction history.
-
C.
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.
-
D.
blockchain-based protocol
A blockchain-based protocol is a decentralized set of rules and procedures encoded on a distributed ledger that governs how participants validate, record, and agree on transactions or data without relying on a central authority.
-
E.
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.
- F. None of above. chosen
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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:01 p.m.