Triple
T15263756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Merge |
E364847
|
entity |
| Predicate | replacedConsensusMechanism |
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: [The Merge, replacedConsensusMechanism, proof-of-work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedConsensusMechanism Context triple: [The Merge, replacedConsensusMechanism, 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.
amendmentMechanism
Indicates the process or rules by which an agreement, document, or system can be formally changed or updated.
-
C.
notAdoptedByConsensus
Indicates that a proposal, decision, or action was not accepted or approved through a consensus-based process among the relevant parties.
-
D.
reconciliationMechanism
Indicates a process or method through which conflicting parties restore harmony, resolve differences, or repair their relationship.
-
E.
hasCurrentConsensus
Indicates that there is a presently agreed-upon or widely accepted position, judgment, or state regarding the related entities.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.