Triple
T9029521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E216132
|
entity |
| Predicate | satoshisPerBCH |
P31033
|
FINISHED |
| Object | 100000000 |
—
|
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: 100000000 | Statement: [Bitcoin Cash, satoshisPerBCH, 100000000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satoshisPerBCH Context triple: [Bitcoin Cash, satoshisPerBCH, 100000000]
-
A.
decimalPlacesRelativeToBitcoin
chosen
Indicates the number of decimal places used to express a value relative to Bitcoin’s standard unit precision.
-
B.
difficultyTargetBits
Indicates the required difficulty level for a task or computation, expressed as a target number of leading zero bits that a valid solution must satisfy.
-
C.
feeRateUnitExample
Indicates the unit of measurement used to express an example fee rate (e.g., per hour, per transaction, per day).
-
D.
secondHalvingYear
Indicates the calendar year in which the second halving event of a recurring, typically periodic, process or quantity occurs.
-
E.
formerCoinDenomination
Indicates that one entity was previously used as a unit of coinage or monetary denomination in the context of the other entity, but is no longer in current use.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a9bcb508190b58751f1772407d4 |
completed | April 1, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:08 p.m.