Triple
T4710968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation SCI |
E104509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | SEC rule framework |
C11529
|
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 rule framework Context triple: [Regulation SCI, instanceOf, SEC rule framework]
-
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.
regulatory framework
chosen
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
C.
self-regulatory organization
A self-regulatory organization is an entity, typically within a specific industry or profession, that creates and enforces rules and standards for its members to promote fair, ethical, and orderly conduct, often under the oversight of a governmental authority.
-
D.
securities industry registration database
A securities industry registration database is a centralized system that stores, tracks, and manages registration, licensing, and regulatory information for firms and individuals participating in the securities markets.
-
E.
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.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:17 p.m.