Triple
T37235173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com DeFi Wallet |
E923552
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non-custodial wallet |
C3931
|
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: non-custodial wallet Context triple: [Crypto.com DeFi Wallet, instanceOf, non-custodial wallet]
-
A.
digital asset custodian
A digital asset custodian is an entity that securely holds, manages, and safeguards clients’ digital assets—such as cryptocurrencies and tokenized securities—using specialized technology, security controls, and regulatory-compliant processes.
-
B.
digital wallet service
chosen
A digital wallet service is an online platform or application that securely stores users’ payment information and enables them to make electronic transactions, manage funds, and access financial services via digital devices.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.