Triple
T2748353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Enforcement of the SEC |
E60923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory enforcement division |
C1024
|
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: regulatory enforcement division Context triple: [Division of Enforcement of the SEC, instanceOf, regulatory enforcement division]
-
A.
regulatory authority
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.
-
B.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
-
C.
government agency division
chosen
A government agency division is a specialized organizational unit within a larger government agency that focuses on a specific set of functions, programs, or policy areas to support the agency’s overall mission.
-
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.
civil rights enforcement agency
A civil rights enforcement agency is a governmental or independent body responsible for investigating discrimination complaints, enforcing civil rights laws, and promoting equal protection and fair treatment for all individuals.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:56 p.m.