Triple
T7593713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Family Insurance |
E179802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mutual 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: mutual insurance company Context triple: [American Family Insurance, instanceOf, mutual 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.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
C.
public consortium
A public consortium is a collaborative alliance of multiple public or publicly accountable organizations that pool resources, expertise, and governance to pursue shared goals or projects in the public interest.
-
D.
public–private partnership company
A public–private partnership company is an entity formed through collaboration between government and private sector organizations to finance, build, and operate projects or services traditionally provided by the public sector.
-
E.
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.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:53 p.m.