Triple
T30644663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ria Money Transfer |
E780087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | remittance company |
C6079
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: remittance company Context triple: [Ria Money Transfer, instanceOf, remittance company]
-
A.
money transfer service
chosen
A money transfer service is a system that securely moves funds from one party to another, often across different accounts, institutions, or geographic locations.
-
B.
payment services provider
A payment services provider is an entity that enables businesses and individuals to send, receive, process, and manage electronic payments securely across various channels and methods.
-
C.
public transit payment platform
A public transit payment platform is a digital system that enables riders to pay fares seamlessly across various transportation services using methods like mobile apps, contactless cards, or online accounts while integrating with transit operators’ ticketing and validation infrastructure.
-
D.
payment technology company
A payment technology company develops and provides digital infrastructure, platforms, and tools that enable secure, efficient, and seamless financial transactions between businesses, consumers, and financial institutions.
-
E.
financial messaging network
A financial messaging network is a secure, standardized communication infrastructure that enables financial institutions to exchange payment, settlement, and transaction-related messages reliably and efficiently.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:29 p.m.