Triple
T23314760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Medical Program |
E590674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | distributed medical education program |
C5447
|
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: distributed medical education program Context triple: [Northern Medical Program, instanceOf, distributed medical education program]
-
A.
medical program
A medical program is an organized course of study or coordinated set of healthcare services designed to educate practitioners or deliver medical care according to defined standards and objectives.
-
B.
medical education site
A medical education site is an online platform that provides structured, evidence-based learning resources and tools to support the training, assessment, and continuing education of healthcare professionals and students.
-
C.
educational program
chosen
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.
-
D.
medical science training program
A medical science training program is a structured educational pathway that equips learners with the scientific knowledge, clinical skills, and professional competencies needed to practice and advance medicine.
-
E.
distance education institution
A distance education institution is an organization that delivers structured educational programs and support services to learners who are geographically separated from instructors, primarily through online or other remote communication technologies.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.