Triple
T38669666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beep card |
E940545
|
entity |
| Predicate | topUpAt |
P27918
|
FINISHED |
| Object | LRT and MRT stations |
—
|
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: LRT and MRT stations | Statement: [Beep card, topUpAt, LRT and MRT stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topUpAt Context triple: [Beep card, topUpAt, LRT and MRT stations]
-
A.
topUpLocations
chosen
Indicates locations where a balance, credit, or value can be increased or recharged for a related account, service, or device.
-
B.
topUpMethod
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
C.
hasATMNetwork
Indicates that an entity operates, participates in, or is connected to a particular automated teller machine (ATM) network for financial transactions.
-
D.
banksHost
Indicates that a financial institution (bank) provides hosting or custodial services for another entity’s assets, accounts, or operations.
-
E.
paySystem
Indicates that one entity provides monetary or other compensation to another entity through a particular method, platform, or mechanism.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.