Triple
T14262147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TARGET2 |
E353547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | real-time gross settlement system |
C8051
|
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: real-time gross settlement system Context triple: [TARGET2, instanceOf, real-time gross settlement system]
-
A.
industry clearing and settlement system
An industry clearing and settlement system is a centralized infrastructure that validates, nets, and finalizes financial transactions between market participants, ensuring accurate, timely, and risk-managed transfer of funds and securities.
-
B.
transaction processing system
A transaction processing system is a software and hardware solution that reliably captures, validates, and records business transactions in real time while ensuring data integrity, consistency, and recoverability.
-
C.
central securities depository
A central securities depository is a specialized financial institution that holds securities in electronic form and facilitates their safekeeping, transfer, and settlement between market participants.
-
D.
Treasury securities account system
A Treasury securities account system is a platform that records, manages, and processes the issuance, ownership, transactions, and servicing (e.g., interest and principal payments) of government debt instruments for investors and institutions.
-
E.
electronic payment system
chosen
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.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.