Triple
T632391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 20022 |
E15950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial messaging standard |
C3605
|
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: financial messaging standard Context triple: [ISO 20022, instanceOf, financial messaging standard]
-
A.
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.
-
B.
messaging standard
chosen
A messaging standard is a defined set of rules and formats that enables different systems or applications to exchange messages in a consistent, interoperable, and reliable way.
-
C.
financial instrument
A financial instrument is a tradable asset or contract that represents a legal agreement involving monetary value, such as stocks, bonds, derivatives, or loans.
-
D.
financial institution
A financial institution is an organization that manages money and financial services, such as accepting deposits, providing loans, facilitating investments, and enabling payment transactions for individuals, businesses, and governments.
-
E.
financial market
A financial market is a system or platform where buyers and sellers trade financial assets such as stocks, bonds, currencies, and derivatives, determining their prices through supply and demand.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:35 p.m.