Triple
T5028715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation G |
E113241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States financial regulation |
C832
|
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: United States financial regulation Context triple: [Regulation G, instanceOf, United States financial regulation]
-
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.
financial reform
Financial reform is the process of redesigning laws, regulations, and institutions in the financial system to improve stability, fairness, transparency, and economic efficiency.
-
C.
central bank supervisory role
The central bank supervisory role encompasses the oversight, regulation, and examination of financial institutions to ensure their safety, soundness, and compliance with prudential standards, thereby safeguarding financial stability and protecting depositors.
-
D.
United States federal commission
A United States federal commission is an independent or semi-independent governmental body established by Congress or the executive branch to investigate, regulate, or advise on specific national issues or policy areas.
-
E.
United States federal policy
chosen
United States federal policy is the body of laws, regulations, and official actions enacted or implemented by the federal government to address national issues and guide public and private behavior across the country.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:36 p.m.