Triple
T37235130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com Visa Card |
E923551
|
entity |
| Predicate | supportsSpendingOf |
—
|
GENERATED |
| Object | cryptocurrencies |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSpendingOf Context triple: [Crypto.com Visa Card, supportsSpendingOf, cryptocurrencies]
-
A.
supportsSpendingCategory
chosen
Indicates that one entity allows, enables, or is compatible with making expenditures in a specified spending category.
-
B.
authorizedSpending
Indicates that an entity has been granted permission to spend or allocate a specified amount of resources, typically funds, under defined conditions.
-
C.
spendingRequires
Indicates that performing a spending action is contingent upon satisfying a specified requirement or condition.
-
D.
overseesSpendingOf
Indicates that one entity has authority to monitor, direct, or control how another entity’s funds or budget are used.
-
E.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another entity.
- 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.