Triple
T37150265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-Chain |
E920342
|
entity |
| Predicate | consensusFamily |
P186467
|
FINISHED |
| Object | Snow family of consensus protocols |
—
|
NE NERFINISHED |
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: Snow family of consensus protocols | Statement: [P-Chain, consensusFamily, Snow family of consensus protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consensusFamily Context triple: [P-Chain, consensusFamily, Snow family of consensus protocols]
-
A.
supportsConsensus
Indicates that one entity endorses, upholds, or contributes to the achievement or maintenance of a shared agreement or collective decision among multiple parties.
-
B.
laterConsensus
Indicates that a consensus or agreed-upon position is reached at a time later than a previously considered or initial consensus.
-
C.
concurrentFamily
Indicates that two or more family-related entities exist or occur during the same time period.
-
D.
usesConsensusType
chosen
Indicates that an entity operates using, is governed by, or is associated with a particular consensus mechanism or consensus type.
-
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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:15 p.m.