Triple
T27639016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin regtest |
E696537
|
entity |
| Predicate | coinAcquisitionMethod |
P5266
|
FINISHED |
| Object | mining blocks locally |
—
|
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: mining blocks locally | Statement: [Bitcoin regtest, coinAcquisitionMethod, mining blocks locally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinAcquisitionMethod Context triple: [Bitcoin regtest, coinAcquisitionMethod, mining blocks locally]
-
A.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
B.
topUpMethod
chosen
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
C.
usedFundingMethods
Indicates that an entity employed specific funding methods to finance an activity, project, or operation.
-
D.
coinIssuer
Indicates that an entity issues, mints, or is responsible for the creation and release of a particular coin or currency.
-
E.
tradeMechanism
Indicates the method or system through which a trade or exchange between parties is conducted.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6318fec0c8190971b4fc1a7df10d3 |
completed | May 2, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:25 p.m.