Triple
T23183002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cash App Card |
E579509
|
entity |
| Predicate | canBeUsedAt |
P96936
|
FINISHED |
| Object | merchants that accept Visa |
—
|
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: merchants that accept Visa | Statement: [Cash App Card, canBeUsedAt, merchants that accept Visa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedAt Context triple: [Cash App Card, canBeUsedAt, merchants that accept Visa]
-
A.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
B.
canBeUsedOver
Indicates that one entity is suitable or valid for use in place of, or in relation to, another entity.
-
C.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
canOperateAt
chosen
Indicates that one entity has the capability, permission, or suitability to function or perform its role at, within, or under the conditions of another entity or context.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f705c14819082c8580a03ed6286 |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.