Triple
T265508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitcoin |
E5715
|
entity |
| Predicate | consensusMechanism |
P8883
|
FINISHED |
| Object | proof-of-work |
—
|
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: proof-of-work | Statement: [Bitcoin, consensusMechanism, proof-of-work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensusMechanism Context triple: [Bitcoin, consensusMechanism, proof-of-work]
-
A.
commitmentThreshold
Indicates the minimum level or degree of commitment required before a particular action, status, or relationship is established or recognized.
-
B.
majorityVote
Indicates that a decision or outcome is determined by the option receiving more than half of the votes among a group.
-
C.
governanceModel
Indicates the type or structure of authority, decision-making, and control that defines how an entity is directed and overseen.
-
D.
hasMajorityLeader
Indicates that one entity serves as the primary or leading decision-making authority (majority leader) for another entity, typically within a governing or organizational body.
-
E.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c8ae480819094f6d1bb0a6d2eb2 |
completed | Feb. 28, 2026, 3:10 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.