Triple
T25256952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Payments Corporation of India |
E633196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | umbrella organization for retail payments |
C8609
|
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: umbrella organization for retail payments Context triple: [National Payments Corporation of India, instanceOf, umbrella organization for retail payments]
-
A.
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.
-
B.
payment network
A payment network is a system that facilitates the authorization, clearing, and settlement of financial transactions between payers, payees, and their financial institutions.
-
C.
payment network
A payment network is a system of interconnected institutions, technologies, and rules that enables the authorization, clearing, and settlement of financial transactions between payers and payees.
-
D.
electronic payment system
An electronic payment system is a digital infrastructure that enables the secure transfer of funds between parties via electronic devices and networks without the need for physical cash or paper-based instruments.
-
E.
payment network operator
chosen
A payment network operator is an entity that manages and maintains the infrastructure, rules, and processes that enable electronic payment transactions to be routed, authorized, cleared, and settled between financial institutions and merchants.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:13 p.m.