Triple
T23040640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Life Insurance Company |
E573724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mutual life insurance company |
C47166
|
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: mutual life insurance company Context triple: [New York Life Insurance Company, instanceOf, mutual life insurance company]
-
A.
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.
-
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 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.
-
E.
multiemployer benefit plan
A multiemployer benefit plan is a collectively bargained employee benefit arrangement maintained by two or more unrelated employers, typically within the same industry, and administered by a joint board of trustees representing both employers and labor unions.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:53 p.m.