Triple
T37235135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com Visa Card |
E923551
|
entity |
| Predicate | offersPerk |
P100194
|
FINISHED |
| Object | rebates on subscription services |
—
|
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: rebates on subscription services | Statement: [Crypto.com Visa Card, offersPerk, rebates on subscription services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersPerk Context triple: [Crypto.com Visa Card, offersPerk, rebates on subscription services]
-
A.
offersPass
Indicates that one entity provides or makes available a pass (such as a ticket, permit, or access credential) to another entity.
-
B.
offersIncentive
chosen
Indicates that one entity provides a reward, benefit, or motivation to another entity to encourage a specific action or behavior.
-
C.
offersAward
Indicates that one entity grants or makes available an award or prize to another entity.
-
D.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
E.
offersAccess
Indicates that one entity provides another entity with the ability or permission to use, enter, or interact with a resource, service, or location.
- 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_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: May 3, 2026, 4:15 p.m.