Triple
T20399317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hospital-Acquired Condition Reduction Program |
E500289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pay-for-performance program |
C40794
|
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: pay-for-performance program Context triple: [Hospital-Acquired Condition Reduction Program, instanceOf, pay-for-performance program]
-
A.
results-based payment mechanism
chosen
A results-based payment mechanism is a contractual arrangement where financial compensation is contingent upon the achievement and verification of predefined performance outcomes or targets.
-
B.
reimbursement program
A reimbursement program is a structured system through which individuals or organizations are repaid for eligible expenses they have incurred, typically after submitting proof of payment and meeting predefined criteria.
-
C.
performance program
A performance program is a structured plan or set of activities designed to enhance, measure, and showcase the effectiveness, efficiency, or artistic quality of an individual, team, or system over a defined period.
-
D.
fiscal policy program
A fiscal policy program is a coordinated set of government actions and rules that use taxation, spending, and borrowing to influence economic activity, growth, and stability.
-
E.
policy program
A policy program is a coordinated set of government or organizational initiatives, actions, and resources designed to achieve specific public or institutional goals through the implementation of formal policies.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:29 a.m.