Triple
T29233591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insurance Regulatory Authority of Kenya |
E741135
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurance regulatory 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: insurance regulatory authority Context triple: [Insurance Regulatory Authority of Kenya, instanceOf, insurance regulatory authority]
-
A.
insurance regulation
Insurance regulation is the framework of laws, rules, and oversight mechanisms that govern how insurance companies operate, protect policyholders, manage risk, and maintain financial solvency.
-
B.
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.
-
C.
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.
-
D.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
-
E.
insurance provider
An insurance provider is an organization that offers risk management products and services by underwriting policies and collecting premiums to compensate policyholders for covered losses.
- 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 12:28 p.m.