Triple
T34026133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | go card |
E872510
|
entity |
| Predicate | supportsTopUpMethods |
—
|
GENERATED |
| Object | online top-up |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTopUpMethods Context triple: [go card, supportsTopUpMethods, online top-up]
-
A.
topUpMethod
chosen
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
B.
hasNolCardTopUpFacilities
Indicates that the subject location or service does not provide facilities for topping up or reloading a Nol card.
-
C.
supportsMobileWallets
Indicates that an entity provides the capability to make or accept payments through mobile wallet services.
-
D.
supportsAllocationMethods
Indicates that one entity enables, is compatible with, or provides mechanisms for using specific allocation methods associated with another entity.
-
E.
supportsAddressTypes
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
- F. None of above.
Provenance (1 batch)
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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:51 a.m.