Triple
T15852926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOT |
E384384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulated bond market segment |
C14021
|
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: regulated bond market segment Context triple: [MOT, instanceOf, regulated bond market segment]
-
A.
regulated market
chosen
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.
-
B.
bond market access program
A bond market access program is a structured initiative that enables eligible issuers—often governments, municipalities, or corporations—to enter or improve their participation in bond markets by providing technical assistance, credit enhancement, or regulatory support.
-
C.
government bond
A government bond is a debt security issued by a national government to raise funds, promising periodic interest payments and the return of principal at maturity, typically considered low-risk relative to other investments.
-
D.
regulated entity
A regulated entity is an organization or individual whose activities are subject to oversight, rules, and enforcement by a governmental or regulatory authority.
-
E.
stock market segment
A stock market segment is a distinct subset of the overall stock market grouped by shared characteristics such as company size, industry, geography, or trading venue to facilitate targeted analysis and investment.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.