Triple
T22416256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solvency Capital Requirement |
E554130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory capital requirement |
C20083
|
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: regulatory capital requirement Context triple: [Solvency Capital Requirement, instanceOf, regulatory capital requirement]
-
A.
Basel Capital Accord
The Basel Capital Accord is an international regulatory framework developed by the Basel Committee on Banking Supervision that sets minimum capital requirements and risk management standards for banks to promote stability in the global financial system.
-
B.
regulatory provision
chosen
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.
-
C.
Basel Accord
The Basel Accord is an international regulatory framework developed by the Basel Committee on Banking Supervision that sets standards for bank capital adequacy, risk management, and supervisory practices to promote stability in the global financial system.
-
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.
regulatory document
A regulatory document is an official written instrument issued by an authority that defines, interprets, or enforces rules, standards, or requirements governing specific activities, entities, or domains.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:46 p.m.