Triple
T7511702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHSU-OSU College of Pharmacy (Portland campus partner) |
E177535
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborative education program |
C21349
|
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: collaborative education program Context triple: [OHSU-OSU College of Pharmacy (Portland campus partner), instanceOf, collaborative education program]
-
A.
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.
-
B.
educational collaboration
chosen
Educational collaboration is a cooperative process in which students, educators, and sometimes external partners work together to share knowledge, skills, and resources to enhance learning outcomes and create meaningful educational experiences.
-
C.
education and outreach program
An education and outreach program is an organized set of activities designed to inform, engage, and empower target audiences through learning opportunities and community-focused communication.
-
D.
educational project
An educational project is a structured learning initiative designed to achieve specific educational objectives through planned activities, resources, and assessments.
-
E.
academic program
An academic program is a structured set of courses, requirements, and learning experiences offered by an educational institution that leads to a specific credential, such as a degree, diploma, or certificate.
- 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:45 p.m.