Triple
T9800626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PULSE network |
E237827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electronic funds transfer network |
C8663
|
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: electronic funds transfer network Context triple: [PULSE network, instanceOf, electronic funds transfer network]
-
A.
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.
-
B.
network of financial institutions
A network of financial institutions is an interconnected system of banks, investment firms, insurers, and other financial entities that interact through transactions, contracts, and information flows to facilitate the movement of capital and manage financial risk.
-
C.
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.
-
D.
payment network
chosen
A payment network is a system that facilitates the authorization, clearing, and settlement of financial transactions between payers, payees, and their financial institutions.
-
E.
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.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:29 p.m.