Triple
T1613589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis Block |
E34662
|
entity |
| Predicate | blockRewardSpendable |
P30431
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Genesis Block, blockRewardSpendable, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockRewardSpendable Context triple: [Genesis Block, blockRewardSpendable, false]
-
A.
firstBlockReward
Indicates the initial reward amount granted for producing or validating the very first block in a blockchain or similar sequential ledger.
-
B.
initialBlockReward
Indicates the reward amount granted for mining or validating the very first block in a blockchain or similar system.
-
C.
blockRewardHalvingIntervalBlocks
Indicates the number of blocks that must be mined before the block reward is reduced (halved) according to the protocol’s schedule.
-
D.
estimatedNumberOfBlocks
Indicates the approximate count of discrete blocks associated with or involved in the given entity or context.
-
E.
rewardFulfilledFor
Indicates that a previously promised or expected reward has been delivered or satisfied for a particular entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a93fedcb108190ad91f938d5eeaaa2 |
completed | March 5, 2026, 8:33 a.m. |
Created at: March 4, 2026, 7:28 p.m.