Triple
T594208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Commodity Futures Trading Commission |
E17343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | derivatives market regulator |
C1181
|
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: derivatives market regulator Context triple: [U.S. Commodity Futures Trading Commission, instanceOf, derivatives market regulator]
-
A.
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.
-
B.
regulatory authority
chosen
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
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 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.
-
E.
financial market
A financial market is a system or platform where buyers and sellers trade financial assets such as stocks, bonds, currencies, and derivatives, determining their prices through supply and demand.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:33 p.m.