Triple
T30407331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin Cash |
E773514
|
entity |
| Predicate | hardForkOf |
P169185
|
FINISHED |
| Object | Bitcoin |
—
|
NE NERFINISHED |
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 | Statement: [Bitcoin Cash, hardForkOf, Bitcoin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardForkOf Context triple: [Bitcoin Cash, hardForkOf, Bitcoin]
-
A.
hardFork
Indicates a protocol change where a blockchain’s rules are modified in a way that is not backward-compatible, causing the chain to split into two divergent versions unless all participants upgrade.
-
B.
hardForkReason
Indicates the reason or justification for performing a hard fork in a system or protocol.
-
C.
hardForkDate
Indicates the date on which a protocol or system undergoes a hard fork, i.e., a non-backward-compatible change that splits or upgrades the network.
-
D.
softForkActivation
Indicates that a protocol change is being activated in a backward-compatible (soft fork) manner within a blockchain or distributed ledger system.
-
E.
supports64bitBlockNumbers
Indicates that the subject is capable of handling or operating with 64-bit block number values.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:04 p.m.