Triple
T4647186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Institute for Medical Documentation and Information |
E102200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health information authority |
C7955
|
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 information authority Context triple: [German Institute for Medical Documentation and Information, instanceOf, health information authority]
-
A.
health authority
chosen
A health authority is an organization or governmental body responsible for overseeing, regulating, and coordinating public health services, policies, and programs within a specific jurisdiction.
-
B.
health ministry
A health ministry is a governmental body responsible for formulating and implementing public health policies, managing healthcare systems, and safeguarding the population’s health and well-being.
-
C.
health publication
A health publication is a periodical or digital resource that provides researched, evidence-based information on medical, wellness, and public health topics for professionals or the general public.
-
D.
public health system
A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
-
E.
public health regulation
Public health regulation is the body of laws, policies, and administrative rules designed to protect and promote population health by controlling risks, guiding health behaviors, and ensuring safe environments, products, and services.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:14 p.m.