Triple

T25261654
Position Surface form Disambiguated ID Type / Status
Subject State Health Benefit Plan of Georgia E633318 entity
Predicate instanceOf P0 FINISHED
Object public employee health benefit plan C7278 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: public employee health benefit plan
Context triple: [State Health Benefit Plan of Georgia, instanceOf, public employee health benefit plan]
  • A. health and welfare benefit plan
    A health and welfare benefit plan is an employer- or organization-sponsored program that provides employees and their dependents with non-retirement benefits such as medical, dental, vision, disability, and life insurance coverage.
  • B. employee benefit plan chosen
    An employee benefit plan is an organized program established by an employer to provide workers with non-wage compensation such as health insurance, retirement savings, paid leave, and other benefits.
  • C. health insurance plan type
    A health insurance plan type is a category of coverage that defines how medical services are accessed, which providers can be used, and how costs are shared between the insurer and the insured.
  • D. 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.
  • E. benefits administration provider
    A benefits administration provider is an organization that manages and streamlines employee benefits programs—such as health insurance, retirement plans, and other perks—on behalf of employers to ensure accurate enrollment, compliance, and ongoing 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_69e75a922ad481908f4f1f884583cb42 completed April 21, 2026, 11:08 a.m.
Created at: April 21, 2026, 1:13 p.m.