Triple
T22416257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solvency Capital Requirement |
E554130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | risk-based capital standard |
C18011
|
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: risk-based capital standard Context triple: [Solvency Capital Requirement, instanceOf, risk-based capital standard]
-
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.
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.
-
C.
risk assessment standard
chosen
A risk assessment standard is a formalized set of principles, criteria, and procedures used to systematically identify, analyze, evaluate, and document risks within a specific domain or industry.
-
D.
risk management agency
A risk management agency is an organization that identifies, assesses, and mitigates potential threats to an entity’s assets, operations, and objectives through strategic planning, analysis, and control measures.
-
E.
option risk measure
An option risk measure is a quantitative metric that evaluates the potential financial loss or variability associated with holding or writing options under uncertain market conditions.
- 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.