Triple
T5894092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solvency II Directive |
E131061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurance regulation |
C19494
|
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 regulation Context triple: [Solvency II Directive, instanceOf, insurance regulation]
-
A.
health insurance law
Health insurance law is the body of legal rules and regulations that governs the creation, coverage, administration, and enforcement of health insurance policies and the rights and obligations of insurers, providers, and insured individuals.
-
B.
health insurance policy instrument
A health insurance policy instrument is a formal contract or mechanism that defines the terms, coverage, premiums, and conditions under which an insurer provides financial protection for an individual’s or group’s healthcare expenses.
-
C.
consumer protection regulation
Consumer protection regulation is a set of laws and rules designed to ensure fair treatment, safety, and accurate information for consumers in their transactions with businesses.
-
D.
Indian regulation
Indian regulation refers to the body of laws, rules, and guidelines enacted by Indian legislative, executive, and regulatory authorities to govern economic, social, and administrative activities within the country.
-
E.
safety regulation
A safety regulation is a formal rule or standard established by authorities or organizations to prevent harm, reduce risk, and protect people, property, and the environment in specific activities or industries.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.