Triple
T35525765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota immunization registry |
E1026667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | immunization information system |
C16823
|
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: immunization information system Context triple: [Minnesota immunization registry, instanceOf, immunization information system]
-
A.
immunization program unit
An immunization program unit is an organizational entity responsible for planning, coordinating, and managing vaccination activities and resources to achieve immunization coverage and public health goals.
-
B.
NIH information system
An NIH information system is an integrated digital platform that manages, stores, and facilitates secure access to biomedical research data, administrative records, and operational information across the National Institutes of Health.
-
C.
global immunization strategy
A global immunization strategy is a coordinated, evidence-based framework for planning, delivering, and monitoring vaccination efforts worldwide to prevent disease, reduce health inequities, and strengthen health systems.
-
D.
electronic health record system
chosen
An electronic health record system is a digital platform that securely collects, stores, manages, and shares patients’ health information to support clinical care, coordination, and decision-making.
-
E.
public health institute
A public health institute is an organization dedicated to protecting and improving population health through research, policy development, education, and the implementation of disease prevention and health promotion 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.