Triple
T31214953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estonian Health Insurance Fund |
E795844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public health insurance organization |
C30957
|
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: public health insurance organization Context triple: [Estonian Health Insurance Fund, instanceOf, public health insurance organization]
-
A.
health insurance provider
A health insurance provider is an organization that offers and manages health coverage plans, collecting premiums and paying for or reimbursing members’ eligible medical expenses according to policy terms.
-
B.
public health insurance scheme
chosen
A public health insurance scheme is a government-organized program that pools public funds to provide defined healthcare coverage and financial protection against medical costs for eligible populations.
-
C.
healthcare provider network
A healthcare provider network is an organized group of doctors, hospitals, and other medical professionals and facilities that contract with a health plan to deliver coordinated care to its members.
-
D.
health insurance exchange
A health insurance exchange is a marketplace, typically organized by a government or authorized entity, where individuals and small businesses can compare, purchase, and enroll in standardized health insurance plans.
-
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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.