Triple
T16772922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaiser Permanente |
E407646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated managed care consortium |
C30046
|
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: integrated managed care consortium Context triple: [Kaiser Permanente, instanceOf, integrated managed care consortium]
-
A.
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.
-
B.
healthcare provider network
chosen
A healthcare provider network is an organized group of doctors, hospitals, and other medical professionals and facilities that contract with a health plan to deliver coordinated care to its members.
-
C.
Integrated Care Boards
Integrated Care Boards are statutory NHS organizations in England responsible for planning, funding, and coordinating health and care services across local systems to improve population health and reduce inequalities.
-
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.
public hospital network
A public hospital network is a coordinated system of government-funded hospitals and healthcare facilities that collaboratively provide accessible, often low-cost or free, medical services to a defined population or region.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.