Triple
T27638558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Foundation |
E696528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bitcoin organization |
C36196
|
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 organization Context triple: [Bitcoin Foundation, instanceOf, Bitcoin organization]
-
A.
blockchain organization
chosen
A blockchain organization is an entity that coordinates people, resources, and processes using blockchain-based infrastructure—often including smart contracts and decentralized governance—to manage operations, assets, and decision-making in a transparent and tamper-resistant manner.
-
B.
Bitcoin community website
A Bitcoin community website is an online platform where Bitcoin enthusiasts, developers, investors, and newcomers can share news, resources, discussions, and tools related to Bitcoin and its ecosystem.
-
C.
Bitcoin Core component
A Bitcoin Core component is a modular part of the Bitcoin Core software responsible for specific functions such as networking, consensus, wallet management, or blockchain data handling within the Bitcoin protocol implementation.
-
D.
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.
-
E.
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.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:25 p.m.