Triple
T37235198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com DeFi Wallet |
E923552
|
entity |
| Predicate | custodyType |
P169184
|
FINISHED |
| Object | non-custodial |
—
|
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: non-custodial | Statement: [Crypto.com DeFi Wallet, custodyType, non-custodial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: custodyType Context triple: [Crypto.com DeFi Wallet, custodyType, non-custodial]
-
A.
custody
Indicates having legal responsibility and authority over the care and control of another entity, typically a child or dependent.
-
B.
custodyModel
chosen
Indicates the type or structure of custodial responsibility or control that one party holds over another party or asset.
-
C.
detentionType
Indicates the specific category or form of detention applied to an entity within a custodial or restrictive context.
-
D.
adoptiveRelationshipType
Indicates the specific nature of an adoptive relationship that exists between two entities (e.g., adoptive parent, adopted child).
-
E.
adoptionType
Indicates the specific category or manner in which an adoption relationship is established or recognized between entities.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.