Triple
T35121403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lifestyle Medicine Core Competencies Program |
E1014174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional education program |
C4632
|
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: professional education program Context triple: [Lifestyle Medicine Core Competencies Program, instanceOf, professional education program]
-
A.
professional development program
chosen
A professional development program is a structured series of learning activities and resources designed to enhance individuals’ skills, knowledge, and competencies for career growth and improved job performance.
-
B.
professional experience program
A professional experience program is a structured initiative that provides participants with practical, real-world work exposure, skill development, and mentorship in a specific industry or field.
-
C.
professional degree
A professional degree is an academic credential specifically designed to prepare individuals for entry into a particular profession by combining theoretical knowledge with practical, career-focused training.
-
D.
professional education stage
A professional education stage is a defined phase in an individual’s formal training pathway focused on acquiring the specialized knowledge, skills, and credentials required for entry into or advancement within a specific profession.
-
E.
educational program
An educational program is an organized set of learning experiences, courses, and activities designed to achieve specific educational goals and outcomes for a defined group of learners.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.