Triple
T33090590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Check. Change. Control. |
E846769
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | blood pressure management program |
C10459
|
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: blood pressure management program Context triple: [Check. Change. Control., instanceOf, blood pressure management program]
-
A.
population health management platform
A population health management platform is a system that aggregates and analyzes clinical, claims, and social data to identify risk, coordinate care, and support interventions that improve health outcomes across defined patient populations.
-
B.
management program
A management program is a structured software or organizational system designed to plan, coordinate, monitor, and optimize resources, processes, and activities to achieve specific goals efficiently.
-
C.
public health program
chosen
A public health program is an organized set of coordinated activities and interventions designed to protect, promote, and improve the health of populations through prevention, education, policy, and services.
-
D.
patient registry support program
A patient registry support program is a structured service that helps design, implement, manage, and optimize patient registries to systematically collect, maintain, and analyze health data for clinical, research, and quality-improvement purposes.
-
E.
medical program
A medical program is an organized course of study or coordinated set of healthcare services designed to educate practitioners or deliver medical care according to defined standards and objectives.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.