Triple
T30407188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Classic |
E773510
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cosmos SDK-based blockchain |
C13962
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Cosmos SDK-based blockchain Context triple: [Terra Classic, instanceOf, Cosmos SDK-based blockchain]
-
A.
blockchain-based protocol
A blockchain-based protocol is a decentralized set of rules and procedures encoded on a distributed ledger that governs how participants validate, record, and agree on transactions or data without relying on a central authority.
-
B.
Algorand protocol feature
An Algorand protocol feature is a specific built-in capability or mechanism of the Algorand blockchain that enhances its security, scalability, consensus, or smart contract functionality.
-
C.
pure proof-of-stake blockchain
A pure proof-of-stake blockchain is a distributed ledger system where block creation and network security are entirely determined by validators’ stake (ownership of the native token), without relying on energy-intensive mining or hybrid consensus mechanisms.
-
D.
private blockchain network
A private blockchain network is a permissioned, access-controlled distributed ledger system where only authorized participants can validate transactions and maintain the shared record.
-
E.
public blockchain
chosen
A public blockchain is a decentralized, permissionless distributed ledger where anyone can join the network, validate transactions, and access the full transaction history.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 29, 2026, 8:04 p.m.