Triple
T32265684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Select American Express Corporate Cards |
E824276
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate charge card product line |
C26850
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: corporate charge card product line Context triple: [Select American Express Corporate Cards, instanceOf, corporate charge card product line]
-
A.
charge card product
chosen
A charge card product is a financial payment instrument that allows cardholders to make purchases on credit with the requirement to pay the full balance by a specified due date, typically without preset spending limits but often with associated fees and rewards.
-
B.
credit card product
A credit card product is a financial instrument issued by a lender that allows consumers or businesses to make purchases or access funds on revolving credit under specified terms, fees, and rewards structures.
-
C.
charge card
A charge card is a payment card that allows users to make purchases on credit with the requirement to pay the full balance by a specified due date each billing cycle.
-
D.
co-branded credit card
A co-branded credit card is a payment card issued through a partnership between a financial institution and a non-financial brand, offering cardholders rewards and benefits tied specifically to that partner brand.
-
E.
credit card
A credit card is a payment card issued by a financial institution that allows the holder to borrow funds up to a preset limit to pay for goods and services, with the obligation to repay the borrowed amount, often with interest.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:42 a.m.