Triple
T7031239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 340B Drug Pricing Program |
E163275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare financing mechanism |
C20679
|
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: healthcare financing mechanism Context triple: [340B Drug Pricing Program, instanceOf, healthcare financing mechanism]
-
A.
vaccine financing mechanism
A vaccine financing mechanism is a structured system of funding arrangements, policies, and instruments designed to mobilize, pool, and allocate financial resources to ensure sustainable, equitable access to vaccines.
-
B.
healthcare compensation system
A healthcare compensation system is a framework that manages and administers payments, reimbursements, and financial incentives for healthcare providers and organizations based on services delivered, performance metrics, and regulatory requirements.
-
C.
health care system
A health care system is an organized network of people, institutions, and resources that delivers medical services and public health interventions to maintain and improve the health of a population.
-
D.
health care delivery model
A health care delivery model is a structured approach that defines how health services are organized, financed, and provided to patients to achieve specific quality, access, and cost outcomes.
-
E.
healthcare cost management company
A healthcare cost management company analyzes, negotiates, and optimizes medical spending for organizations and individuals to reduce costs while maintaining quality of care.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:35 p.m.