Triple
T1613581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis Block |
E34662
|
entity |
| Predicate | subsidy |
P8142
|
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: [Genesis Block, subsidy, 50 BTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsidy Context triple: [Genesis Block, subsidy, 50 BTC]
-
A.
subsidizedInterest
Indicates that the interest on a loan or financial obligation is partially or fully paid or reduced by a third party, typically a government or institution, rather than borne entirely by the borrower.
-
B.
subsidiaryProgram
Indicates that one program operates under, and is organizationally subordinate to, another primary or parent program.
-
C.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
D.
carriesMonetaryGrant
chosen
Indicates that one entity provides or includes a monetary grant for another entity or purpose.
-
E.
compensated
Indicates that one entity provides payment or some form of recompense to another entity in return for goods, services, or loss incurred.
- 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.