Triple
T3524615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethereum blockchain |
E74507
|
entity |
| Predicate | originalConsensusMechanism |
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: [Ethereum blockchain, originalConsensusMechanism, proof-of-work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalConsensusMechanism Context triple: [Ethereum blockchain, originalConsensusMechanism, proof-of-work]
-
A.
consensusMechanism
chosen
Indicates the method or protocol by which multiple participants in a distributed system agree on a single, consistent state or outcome.
-
B.
mainMiningMethod
Indicates the primary mining technique or process predominantly used in extracting resources at a given site or operation.
-
C.
consensusRole
Indicates that an entity participates in a consensus process with a specific functional role (e.g., proposer, validator, leader, or follower) within that agreement mechanism.
-
D.
viewOnConsensus
Indicates the stance or opinion an entity holds regarding a consensus or commonly agreed-upon position.
-
E.
initialBlockReward
Indicates the reward amount granted for mining or validating the very first block in a blockchain or similar system.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.