Triple
T10978297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDIC insurance limit |
E259429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial regulatory concept |
C18703
|
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: financial regulatory concept Context triple: [FDIC insurance limit, instanceOf, financial regulatory concept]
-
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 regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
-
C.
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.
-
D.
regulatory framework
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.
-
E.
financial legislation
chosen
Financial legislation comprises the laws and regulations that govern the creation, management, oversight, and stability of financial systems, markets, institutions, and transactions.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.