Triple
T11351912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalanche |
E268856
|
entity |
| Predicate | consensusType |
P8883
|
FINISHED |
| Object | proof-of-stake |
—
|
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-stake | Statement: [Avalanche, consensusType, proof-of-stake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensusType Context triple: [Avalanche, consensusType, proof-of-stake]
-
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.
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.
-
C.
quorumType
Indicates the specific rule or threshold used to determine when a quorum is achieved for a decision-making body or process.
-
D.
finalityType
Indicates the specific kind or category of finality or conclusiveness that applies to a given situation, decision, or state.
-
E.
adoptedByConsensus
Indicates that a decision, action, or change was formally accepted through a consensus process among the relevant participants.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80148e2048190a716b515d78efdd1 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e6f8aeb4819080476f16a69b2ee3 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.