Triple
T11397190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com |
E270006
|
entity |
| Predicate | supportsFiatOnRamp |
P99088
|
FINISHED |
| Object | bank transfer |
—
|
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: bank transfer | Statement: [Crypto.com, supportsFiatOnRamp, bank transfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFiatOnRamp Context triple: [Crypto.com, supportsFiatOnRamp, bank transfer]
-
A.
supportsMobileWallets
Indicates that an entity provides the capability to make or accept payments through mobile wallet services.
-
B.
canUphold
Indicates that an entity has the ability or capacity to maintain, support, or sustain another entity, condition, or standard.
-
C.
supportsAddressTypes
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
-
D.
supportsOpenLoopPayments
Indicates that an entity enables or is compatible with open-loop payment methods, where transactions are processed over general-purpose payment networks rather than a closed, proprietary system.
-
E.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
- F. None of above. chosen
Provenance (4 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80019d3d48190a2f473deb6eae33a |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.