Triple
T3506713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moda Health |
E74093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | employee benefits company |
C423
|
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: employee benefits company Context triple: [Moda Health, instanceOf, employee benefits company]
-
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.
employee benefits law
Employee benefits law governs the creation, administration, and regulation of employer-sponsored benefit plans—such as health insurance, retirement, and disability programs—ensuring compliance with legal standards and protection of employees’ rights.
-
C.
company
chosen
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
-
D.
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.
-
E.
social security benefit
A social security benefit is a government-provided payment or service intended to support individuals’ income, health, or well-being in situations such as retirement, disability, unemployment, or low income.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.