Triple

T7899355
Position Surface form Disambiguated ID Type / Status
Subject P2PKH E183408 entity
Predicate network P2637 FINISHED
Object Bitcoin mainnet E5715 NE 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: Bitcoin mainnet | Statement: [P2PKH, network, Bitcoin mainnet]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bitcoin mainnet
Context triple: [P2PKH, network, Bitcoin mainnet]
  • A. Bitcoin Core
    Bitcoin Core is the open-source software implementation that serves as the primary full node and wallet for the Bitcoin network, maintaining the blockchain and enforcing consensus rules.
  • B. Bitcoin Cash
    Bitcoin Cash is a decentralized cryptocurrency that forked from Bitcoin to offer faster, cheaper peer-to-peer payments through larger block sizes.
  • C. Bitcoin chosen
    Bitcoin is a decentralized digital cryptocurrency that operates without a central bank, enabling peer-to-peer transactions secured by blockchain technology.
  • D. Bitcoin testnet
    Bitcoin testnet is a parallel Bitcoin blockchain used by developers and testers to experiment with transactions and applications using valueless test coins instead of real bitcoin.
  • E. bitcoin-cli
    bitcoin-cli is the command-line interface tool for interacting with a Bitcoin Core node, allowing users to issue RPC commands and manage node operations.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca828d13088190b222be7aa9f9315c completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a3dc2208190a6fea93b60b8daca completed March 31, 2026, 3:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbdfd2dbbc8190b7b1e45b7f0b7515 completed March 31, 2026, 2:53 p.m.
Created at: March 30, 2026, 5:01 p.m.