Triple
T37235130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com Visa Card |
E923551
|
entity |
| Predicate | supportsSpendingOf |
P24220
|
FINISHED |
| Object | cryptocurrencies |
—
|
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: cryptocurrencies | Statement: [Crypto.com Visa Card, supportsSpendingOf, cryptocurrencies]
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 (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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.