Triple
T1448157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazon Pay |
E31220
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | Amazon Pay |
E31220
|
NE 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: Amazon Pay | Statement: [Amazon Pay, brand, Amazon Pay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amazon Pay Context triple: [Amazon Pay, brand, Amazon Pay]
-
A.
Amazon Pay
chosen
Amazon Pay is a digital payment service that lets customers use their Amazon accounts to make secure purchases and payments on third-party websites and apps.
-
B.
PayPal
PayPal is a leading global online payment platform that enables individuals and businesses to send, receive, and manage digital payments securely over the internet.
-
C.
Stripe
Stripe is a leading financial technology company that provides online payment processing and related services for internet businesses worldwide.
-
D.
MobilePay
MobilePay is a popular Nordic mobile payment app that allows users to send and receive money, pay in stores and online, and manage everyday transactions via their smartphones.
-
E.
Google Pay
Google Pay is a digital wallet and online payment platform developed by Google that enables users to make secure contactless payments, in-app purchases, and online transactions using their devices.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55aa7dc8190aa7452d80ec8305e |
completed | March 1, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad08c229808190af9936b481390170 |
completed | March 8, 2026, 5:27 a.m. |
Created at: March 1, 2026, 8 p.m.