Triple
T27638822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pay-to-Witness-Script-Hash |
E696534
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bitcoin output type |
C23140
|
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 output type Context triple: [Pay-to-Witness-Script-Hash, instanceOf, Bitcoin output type]
-
A.
Bitcoin transaction output type
chosen
A Bitcoin transaction output type defines the specific script format and spending conditions that determine how and by whom the associated bitcoins can later be spent.
-
B.
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.
-
C.
Bitcoin Core command-line utility
A Bitcoin Core command-line utility is a text-based tool that allows users and scripts to interact with a Bitcoin Core node for configuration, control, and blockchain-related operations.
-
D.
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.
-
E.
Bitcoin RPC client
A Bitcoin RPC client is a software component that communicates with a Bitcoin node via its JSON-RPC interface to issue commands, query blockchain data, and manage wallets or transactions programmatically.
- 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.