Triple
T18723900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil de résolution unique |
E457848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bank resolution authority |
C1181
|
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: bank resolution authority Context triple: [Conseil de résolution unique, instanceOf, bank resolution authority]
-
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.
bank failure
A bank failure is the collapse or closure of a bank when it can no longer meet its financial obligations to depositors and creditors, typically resulting in regulatory intervention and resolution actions.
-
D.
organ of the European Systemic Risk Board
An organ of the European Systemic Risk Board is a formal institutional body within the ESRB’s governance structure that performs specific functions related to the identification, assessment, and mitigation of systemic risks to the EU financial system.
-
E.
regulatory authority
chosen
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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.