Triple
T13184102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Employees Insurance Company |
E313802
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | auto insurance provider |
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: auto insurance provider Context triple: [Government Employees Insurance Company, instanceOf, auto insurance provider]
-
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.
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.
-
D.
insurance salesman
An insurance salesman is a professional who identifies clients' coverage needs and sells them appropriate insurance policies while explaining terms, benefits, and costs.
-
E.
transport brand
A transport brand is a conceptual class representing a company or entity that provides transportation services or products, characterized by attributes like name, logo, service types, and reputation, and behaviors such as marketing, service delivery, and customer support.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:15 p.m.