Triple
T22460734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutuelle de L’assurance contre L’incendie |
E555221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fire insurance company |
C19822
|
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: fire insurance company Context triple: [Mutuelle de L’assurance contre L’incendie, instanceOf, fire insurance company]
-
A.
property and casualty insurer
chosen
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.
-
B.
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.
-
C.
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.
-
D.
deposit insurance scheme
A deposit insurance scheme is a system, typically run or backed by a government or central authority, that guarantees bank customers will be repaid their deposits up to a specified limit if their financial institution fails.
-
E.
engineering insurance company
An engineering insurance company is a specialized insurer that provides coverage for risks associated with engineering projects, machinery, construction works, and related technical operations.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:48 p.m.