Triple
T4214479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Health Service System |
E93981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public benefits administrator |
C15357
|
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 benefits administrator Context triple: [San Francisco Health Service System, instanceOf, public benefits administrator]
-
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.
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.
-
C.
welfare benefit
A welfare benefit is a government-provided or mandated form of financial or in-kind assistance intended to support individuals or households in meeting basic living needs and promoting social well-being.
-
D.
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.
-
E.
dental benefits provider
A dental benefits provider is an organization that designs, manages, and administers dental insurance or discount plans, coordinating with employers, members, and dental care providers to facilitate and reimburse covered oral health services.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:04 p.m.