Triple
T22460745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AXA |
E555221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurance group |
C46335
|
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 group Context triple: [AXA, instanceOf, insurance group]
-
A.
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.
-
B.
credit insurance company
A credit insurance company is a financial institution that protects businesses against losses from customers’ non-payment of commercial debts, typically due to insolvency or protracted default.
-
C.
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.
-
D.
insurance company program participant
An insurance company program participant is an individual or entity enrolled in and actively taking part in a specific insurance-related program, such as a wellness, risk management, or incentive initiative, offered by an insurance provider.
-
E.
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.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:48 p.m.