Triple
T37235127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crypto.com Visa Card |
E923551
|
entity |
| Predicate | hasPaymentNetwork |
P89771
|
FINISHED |
| Object | Visa |
—
|
NE NERFINISHED |
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: Visa | Statement: [Crypto.com Visa Card, hasPaymentNetwork, Visa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaymentNetwork Context triple: [Crypto.com Visa Card, hasPaymentNetwork, Visa]
-
A.
paymentNetworkType
chosen
Indicates the type or category of payment network through which a payment is processed or routed.
-
B.
paymentNetworkScope
Indicates the extent or domain within which a payment network operates or is considered applicable in the relationship.
-
C.
paymentNetworkRole
Indicates the specific function or responsibility an entity has within a payment network (such as issuer, acquirer, or processor).
-
D.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
E.
paymentSystem
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
- 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_6a0048697bd081909073640666ca6a96 |
completed | May 10, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_6a0047bf3c248190a9ac97a7afdfe2cb |
completed | May 10, 2026, 8:54 a.m. |
Created at: May 3, 2026, 4:15 p.m.