Triple
T35903943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai Health Promotion Foundation |
E1038421
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health promotion agency |
C20647
|
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 promotion agency Context triple: [Thai Health Promotion Foundation, instanceOf, health promotion agency]
-
A.
health promotion unit
A health promotion unit is an organizational entity dedicated to planning, implementing, and evaluating strategies that improve population health and prevent disease through education, policy, and community-based interventions.
-
B.
health agency
chosen
A health agency is an organization responsible for planning, coordinating, and delivering public health services, policies, and programs to protect and improve the health of a population.
-
C.
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.
-
D.
health authority
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.
-
E.
health and social support agency
A health and social support agency is an organization that provides medical, psychological, and social services to individuals and communities to promote well-being and address health-related and social needs.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.