Triple
T1613480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satoshi Nakamoto |
E34660
|
entity |
| Predicate | genesisBlockReward |
P8895
|
FINISHED |
| Object | 50 BTC |
—
|
LITERAL 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: 50 BTC | Statement: [Satoshi Nakamoto, genesisBlockReward, 50 BTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genesisBlockReward Context triple: [Satoshi Nakamoto, genesisBlockReward, 50 BTC]
-
A.
initialBlockReward
Indicates the reward amount granted for mining or validating the very first block in a blockchain or similar system.
-
B.
firstBlockReward
chosen
Indicates the initial reward amount granted for producing or validating the very first block in a blockchain or similar sequential ledger.
-
C.
genesisBlockHash
Indicates the hash value that uniquely identifies the genesis (first) block of a blockchain or ledger.
-
D.
blockRewardHalvingIntervalBlocks
Indicates the number of blocks that must be mined before the block reward is reduced (halved) according to the protocol’s schedule.
-
E.
firstHalvingYear
Indicates the calendar year in which the first halving event associated with an entity (such as a cryptocurrency’s block reward) occurs.
- F. None of above.
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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.