Triple
T29343856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aviva Elite |
E744108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurance company subsidiary |
C54872
|
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 company subsidiary Context triple: [Aviva Elite, instanceOf, insurance company subsidiary]
-
A.
insurance company division
An insurance company division is an organizational unit within an insurance firm responsible for managing specific product lines, markets, or operational functions such as underwriting, claims, or customer service.
-
B.
reinsurance company division
A reinsurance company division is an organizational unit within a reinsurance firm responsible for managing specific lines of business, geographic regions, or functional activities such as underwriting, risk assessment, and client relationships.
-
C.
insurance group
An insurance group is a collection of related insurance companies under common ownership or control that coordinate to offer a range of insurance products and services.
-
D.
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.
-
E.
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.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:35 p.m.