Triple
T30407195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Classic |
E773510
|
entity |
| Predicate | usesConsensusEngine |
P8883
|
FINISHED |
| Object | Tendermint |
—
|
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: Tendermint | Statement: [Terra Classic, usesConsensusEngine, Tendermint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesConsensusEngine Context triple: [Terra Classic, usesConsensusEngine, Tendermint]
-
A.
usesConsensusType
Indicates that an entity operates using, is governed by, or is associated with a particular consensus mechanism or consensus type.
-
B.
supportsConsensus
Indicates that one entity endorses, upholds, or contributes to the achievement or maintenance of a shared agreement or collective decision among multiple parties.
-
C.
hasCurrentConsensus
Indicates that there is a presently agreed-upon or widely accepted position, judgment, or state regarding the related entities.
-
D.
consensusMechanism
chosen
Indicates the method or protocol by which multiple participants in a distributed system agree on a single, consistent state or outcome.
-
E.
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.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 8:04 p.m.