Triple
T20003268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iPhone 6 |
E494387
|
entity |
| Predicate | applePayUsage |
P15672
|
FINISHED |
| Object | in-store payments only via NFC |
—
|
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: in-store payments only via NFC | Statement: [iPhone 6, applePayUsage, in-store payments only via NFC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applePayUsage Context triple: [iPhone 6, applePayUsage, in-store payments only via NFC]
-
A.
supportsTapToPay
chosen
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
hasDigitalWallet
Indicates that an entity possesses or is associated with a digital wallet for storing and managing digital payment instruments or assets.
-
C.
allowsAppleCashFamilySharing
Indicates that an entity permits the use or sharing of Apple Cash within a family sharing group.
-
D.
canPay
Indicates that one entity has the ability or authorization to make a payment to another entity or to settle a specified obligation.
-
E.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a2e34481908a495cc5d077c41f |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.