Triple
T10412683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bond Connect |
E245430
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bond market access program |
C28051
|
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: bond market access program Context triple: [Bond Connect, instanceOf, bond market access program]
-
A.
stock connect program
A stock connect program is a cross-border trading mechanism that links two or more stock exchanges, allowing investors in one market to buy and sell eligible shares listed on another market through a regulated, interconnected platform.
-
B.
broker
A broker is an intermediary entity that facilitates transactions or negotiations between parties, typically in exchange for a fee or commission.
-
C.
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.
-
D.
fixed-income transparency system
A fixed-income transparency system is a platform that collects, standardizes, and disseminates real-time and historical bond and other fixed-income trade and quote data to improve market visibility, price discovery, and regulatory oversight.
-
E.
regulated market
A regulated market is an economic system in which the buying and selling of goods, services, or financial instruments operate under rules and oversight imposed by a governing authority to ensure fairness, stability, and compliance with legal standards.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:10 p.m.