Triple
T26137391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GoTo Group |
E659417
|
entity |
| Predicate | hasDigitalWalletService |
P89772
|
FINISHED |
| Object | GoPay |
—
|
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: GoPay | Statement: [GoTo Group, hasDigitalWalletService, GoPay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalWalletService Context triple: [GoTo Group, hasDigitalWalletService, GoPay]
-
A.
hasDigitalWallet
Indicates that an entity possesses or is associated with a digital wallet for storing and managing digital payment instruments or assets.
-
B.
hasDigitalCard
Indicates that an entity possesses or is associated with a digital card (such as an electronic ID, membership, or payment card).
-
C.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
D.
supportsMobileWallets
chosen
Indicates that an entity provides the capability to make or accept payments through mobile wallet services.
-
E.
hasDigitalSystem
Indicates that an entity possesses, uses, or is equipped with a digital system (such as software, hardware, or an integrated digital platform).
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 8:18 p.m.