Triple
T18136960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principles for Financial Market Infrastructures |
E434160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial market infrastructure standard |
C39695
|
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 market infrastructure standard Context triple: [Principles for Financial Market Infrastructures, instanceOf, financial market infrastructure standard]
-
A.
financial market infrastructure company
A financial market infrastructure company provides the core systems, platforms, and services that enable the trading, clearing, settlement, and reporting of financial instruments in a safe, efficient, and regulated manner.
-
B.
financial market identifier registry
A financial market identifier registry is a centralized system that assigns, maintains, and provides standardized unique identifiers for financial markets, venues, and related entities to support accurate reference, trading, and regulatory reporting.
-
C.
trade finance standard
A trade finance standard is a formalized set of rules, data formats, and processes that harmonize how financial institutions, corporates, and other parties manage, document, and execute trade-related financing and risk mitigation.
-
D.
financial market committee
A financial market committee is a group of experts and stakeholders convened to monitor, evaluate, and guide policies or decisions affecting financial markets and their stability.
-
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. chosen
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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.