Triple
T7579740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAG-AFTRA Health Plan and Pension Plan |
E179455
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multiemployer benefit plan |
C22533
|
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: multiemployer benefit plan Context triple: [SAG-AFTRA Health Plan and Pension Plan, instanceOf, multiemployer benefit plan]
-
A.
employee benefit plan
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.
-
B.
pension plan
A pension plan is a long-term savings and investment arrangement, typically sponsored by an employer or government, that provides individuals with regular income payments after retirement based on contributions and plan rules.
-
C.
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.
-
D.
public benefits administrator
A public benefits administrator oversees the implementation, management, and compliance of government assistance programs to ensure eligible individuals and families receive appropriate services and support.
-
E.
ERISA provision
An ERISA provision is a specific rule or requirement within the Employee Retirement Income Security Act that governs the administration, funding, fiduciary duties, and participant rights related to employer-sponsored benefit plans.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:52 p.m.