Triple
T21802017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IOSCO Principles of Securities Regulation |
E538260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | securities regulation standard |
C31860
|
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: securities regulation standard Context triple: [IOSCO Principles of Securities Regulation, instanceOf, securities regulation standard]
-
A.
securities regulation law
Securities regulation law is the body of rules and principles governing the issuance, trading, disclosure, and oversight of financial instruments such as stocks and bonds to protect investors and maintain fair, efficient markets.
-
B.
securities commission
A securities commission is a government or regulatory authority responsible for overseeing and enforcing laws governing securities markets to protect investors and ensure fair, transparent, and efficient trading.
-
C.
U.S. Securities and Exchange Commission procedure
U.S. Securities and Exchange Commission procedure refers to the formal processes, rules, and steps the SEC follows to regulate securities markets, enforce federal securities laws, review filings, and conduct investigations and administrative actions.
-
D.
regulations
chosen
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
E.
self-regulatory agreement
A self-regulatory agreement is a voluntary, collectively adopted set of rules and standards through which an industry or group governs its own behavior without direct external enforcement.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:53 p.m.