Triple
T34712832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation S-K |
E1000693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SEC regulation |
C2201
|
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: SEC regulation Context triple: [Regulation S-K, instanceOf, SEC regulation]
-
A.
securities regulation law
chosen
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.
financial services regulation
Financial services regulation encompasses the laws, rules, and supervisory frameworks that govern financial institutions and markets to ensure stability, integrity, consumer protection, and fair competition.
-
C.
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.
-
D.
financial regulatory authority
A financial regulatory authority is an organization empowered by law to oversee, supervise, and enforce rules governing financial markets and institutions to ensure stability, integrity, and consumer protection.
-
E.
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.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.