Triple
T15919600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRA regulations of the Federal Reserve Board |
E386057
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prudential supervision rule |
C3451
|
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: prudential supervision rule Context triple: [CRA regulations of the Federal Reserve Board, instanceOf, prudential supervision rule]
-
A.
insurance regulation
Insurance regulation is the framework of laws, rules, and oversight mechanisms that govern how insurance companies operate, protect policyholders, manage risk, and maintain financial solvency.
-
B.
central bank supervisory role
chosen
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.
-
C.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
D.
bail-in provision
A bail-in provision is a contractual or statutory mechanism that allows a failing financial institution’s creditors and, in some cases, shareholders to have their claims written down or converted into equity to recapitalize the institution and avoid taxpayer-funded bailouts.
-
E.
regulations
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.