Triple
T36674437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Family and Community Medicine |
E905506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | family medicine department |
C6305
|
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: family medicine department Context triple: [Department of Family and Community Medicine, instanceOf, family medicine department]
-
A.
medical family
A medical family is a group of related individuals whose health histories, genetic traits, and shared environmental factors collectively influence their medical risks, care, and treatment planning.
-
B.
medical academic department
chosen
A medical academic department is an organizational unit within a medical school or academic health center responsible for education, research, and clinical services in a specific medical specialty or discipline.
-
C.
college of medicine
A college of medicine is an academic institution within a university that provides education, training, and research in medical and health-related fields to prepare students for careers as physicians and other healthcare professionals.
-
D.
medical practice
A medical practice is an organized healthcare setting where licensed medical professionals diagnose, treat, and manage patients’ health conditions, often within a specific specialty or range of services.
-
E.
community health center
A community health center is a local, patient-centered facility that provides accessible, comprehensive primary and preventive healthcare services, often focusing on underserved populations regardless of their ability to pay.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.