Triple
T16604587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Health Protection Principal Committee |
E403417
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public health committee |
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: public health committee Context triple: [Australian Health Protection Principal Committee, instanceOf, public health committee]
-
A.
public health organisation
A public health organisation is an entity, typically governmental or non-profit, that plans, implements, and evaluates programs and policies to protect and improve the health of populations.
-
B.
public health partnership
A public health partnership is a collaborative alliance among governmental agencies, community organizations, healthcare providers, and other stakeholders that coordinates resources and efforts to improve population health outcomes and address public health challenges.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.