Triple
T33791269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Heritage Life Insurance Company of America |
E865936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supplemental insurance provider |
C52007
|
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: supplemental insurance provider Context triple: [Family Heritage Life Insurance Company of America, instanceOf, supplemental insurance provider]
-
A.
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.
-
B.
insurance provider
chosen
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.
-
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.
insurance company subsidiary
An insurance company subsidiary is a legally distinct entity owned or controlled by a parent insurance company that conducts specific insurance or related financial services under its own structure and branding.
-
E.
reinsurer
A reinsurer is a company that provides insurance to other insurance companies by assuming part of their risk exposure in exchange for a share of the premiums.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.