Triple
T28532668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolescent Sexual Health Programs |
E722083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health education initiative |
C5312
|
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 education initiative Context triple: [Adolescent Sexual Health Programs, instanceOf, health education initiative]
-
A.
health education program
chosen
A health education program is an organized set of learning activities designed to increase individuals’ knowledge, skills, and motivation to adopt and maintain healthy behaviors.
-
B.
health education centre
A health education centre is a facility dedicated to providing individuals and communities with information, resources, and programs that promote healthy behaviors, disease prevention, and overall well-being.
-
C.
health and safety initiative
A health and safety initiative is a coordinated program of policies, practices, and interventions designed to prevent injuries and illnesses, promote well-being, and ensure a safe environment for individuals in a specific setting or community.
-
D.
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.
-
E.
health professions education center
A health professions education center is an academic and clinical hub that coordinates, delivers, and advances interprofessional education, training, and research for current and future healthcare providers.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:29 a.m.