Triple
T4834462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Systemic Risk Board |
E108023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | macroprudential oversight body |
C1299
|
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: macroprudential oversight body Context triple: [European Systemic Risk Board, instanceOf, macroprudential oversight body]
-
A.
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.
-
B.
financial regulatory authority
chosen
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.
-
C.
financial oversight office
A financial oversight office is an organizational unit responsible for monitoring, reviewing, and ensuring the accuracy, compliance, and integrity of an entity’s financial activities and reporting.
-
D.
central banking system
A central banking system is a national financial institution framework responsible for issuing currency, managing monetary policy, regulating the money supply, and overseeing the stability and liquidity of the banking sector.
-
E.
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.
- 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_69bd43fbe444819085cb970706ef73f7 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:25 p.m.