Triple
T34469993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Mobile |
E884879
|
entity |
| Predicate | hasTopUpMethod |
P5266
|
FINISHED |
| Object | credit card |
—
|
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: credit card | Statement: [Public Mobile, hasTopUpMethod, credit card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopUpMethod Context triple: [Public Mobile, hasTopUpMethod, credit card]
-
A.
topUpMethod
chosen
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
B.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
C.
hasOpalTopUpMachine
Indicates that a location or facility is equipped with an Opal card top-up machine for adding credit or purchasing travel value.
-
D.
hasRechargeSource
Indicates that an entity receives or can obtain electrical power or energy from a specified source for recharging.
-
E.
hasGoCardTopUp
Indicates that an entity has performed or is associated with a Go Card balance top-up transaction.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 2:01 a.m.