Triple
T28540018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | federal Anti-Kickback Statute |
E722265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health care fraud and abuse law |
C18687
|
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: health care fraud and abuse law Context triple: [federal Anti-Kickback Statute, instanceOf, health care fraud and abuse law]
-
A.
health insurance law
Health insurance law is the body of legal rules and regulations that governs the creation, coverage, administration, and enforcement of health insurance policies and the rights and obligations of insurers, providers, and insured individuals.
-
B.
health law program
A health law program is an academic or training course of study that focuses on the legal, regulatory, and ethical issues governing healthcare systems, providers, patients, and public health policy.
-
C.
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.
-
D.
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.
-
E.
health legislation
chosen
Health legislation comprises the laws and regulations enacted to organize, finance, deliver, and oversee public and private health services, protect public health, and safeguard patients’ rights.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:34 a.m.