Triple
T20804695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | enhanced FMAP |
E512125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal Medicaid financing mechanism |
C17957
|
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: federal Medicaid financing mechanism Context triple: [enhanced FMAP, instanceOf, federal Medicaid financing mechanism]
-
A.
healthcare financing mechanism
A healthcare financing mechanism is a structured method by which funds are collected, pooled, and allocated to pay for health services within a health system.
-
B.
federal reimbursement formula
chosen
A federal reimbursement formula is a standardized method used by the federal government to calculate how much money it will repay to states, agencies, or organizations for eligible costs under specific programs or regulations.
-
C.
Medicaid program integrity entity
A Medicaid program integrity entity is an organization or unit responsible for preventing, detecting, and addressing fraud, waste, and abuse within the Medicaid program to ensure proper use of funds and compliance with regulations.
-
D.
Medicaid benefit
A Medicaid benefit is a specific health care service, item, or support that Medicaid covers for eligible beneficiaries under federal and state program rules.
-
E.
component of the Centers for Medicare & Medicaid Services
A component of the Centers for Medicare & Medicaid Services is an organizational unit within CMS responsible for specific functions such as policy development, program administration, oversight, or support related to Medicare, Medicaid, and other health coverage programs.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:40 p.m.