Triple
T26577890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMS Alliance to Modernize Healthcare |
E666994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Healthcare research organization |
C425
|
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 research organization Context triple: [CMS Alliance to Modernize Healthcare, instanceOf, Healthcare research organization]
-
A.
healthcare technology research organization
A healthcare technology research organization is an entity that investigates, develops, and evaluates innovative digital and medical technologies to improve patient care, clinical workflows, and health system outcomes.
-
B.
research hospital organization
A research hospital organization is a healthcare institution that integrates patient care with systematic scientific investigation to develop, test, and translate new medical knowledge, treatments, and technologies into clinical practice.
-
C.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
D.
health systems research organisation
A health systems research organisation is an entity that systematically studies how health services are organized, financed, delivered, and governed to generate evidence that improves the performance, equity, and resilience of health systems.
-
E.
research and development organization
chosen
A research and development organization is an entity dedicated to systematically investigating ideas and technologies to create new knowledge, products, or processes and improve existing ones.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:01 a.m.