Triple
T4343877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basel Committee on Banking Supervision |
E97852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | banking regulatory committee |
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: banking regulatory committee Context triple: [Basel Committee on Banking Supervision, instanceOf, banking regulatory committee]
-
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.
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.
-
C.
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.
-
D.
banking law
Banking law is the body of legal rules and regulations that governs the creation, operation, and supervision of banks and other financial institutions, as well as their relationships with customers, regulators, and markets.
-
E.
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.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:14 p.m.