Triple
T27707835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insurance Capital Standard |
E698600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prudential regulatory standard |
C53192
|
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: prudential regulatory standard Context triple: [Insurance Capital Standard, instanceOf, prudential regulatory standard]
-
A.
Solvency II Directive
The Solvency II Directive is a European Union regulatory framework that sets risk-based capital, governance, and reporting requirements for insurance and reinsurance companies to ensure their financial soundness and policyholder protection.
-
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.
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.
-
D.
regulatory provision
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.
-
E.
Solvency II concept
A Solvency II concept is any regulatory notion, measure, or construct defined within the Solvency II framework to assess, manage, and report the risks and capital adequacy of insurance and reinsurance undertakings in the European Union.
- F. None of above. chosen
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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3 p.m.