Triple
T29343857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aviva Elite |
E744108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized insurance provider |
C52007
|
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: specialized insurance provider Context triple: [Aviva Elite, instanceOf, specialized insurance provider]
-
A.
insurance provider
chosen
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.
-
B.
property and casualty insurer
A property and casualty insurer is a company that provides insurance coverage to protect individuals and businesses against financial losses resulting from damage to property and legal liability for injuries or damage to others.
-
C.
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.
-
D.
specialized institution
A specialized institution is an organization dedicated to a specific field or function, providing focused services, expertise, or education within that domain.
-
E.
insurance pioneer
An insurance pioneer is an individual or organization that introduces groundbreaking concepts, practices, or technologies that fundamentally reshape how risk is assessed, priced, and managed within the insurance industry.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:35 p.m.