Triple
T19943554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Write Your Own insurance companies |
E479366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | private 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: private insurance company Context triple: [Write Your Own insurance companies, instanceOf, private 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.
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.
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.
-
D.
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.
-
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.
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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:54 p.m.