Triple
T5279199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countway Library of Medicine |
E119448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | academic medical library |
C59
|
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: academic medical library Context triple: [Countway Library of Medicine, instanceOf, academic medical library]
-
A.
academic health sciences center
An academic health sciences center is an integrated institution that combines clinical care, health professions education, and biomedical research, typically linking a medical school with one or more teaching hospitals and related health programs.
-
B.
academic library system
chosen
An academic library system manages the acquisition, organization, discovery, circulation, and preservation of scholarly resources to support the teaching, learning, and research needs of an academic institution.
-
C.
medical academic department
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.
-
D.
public academic health center
A public academic health center is a publicly funded medical institution that integrates patient care, health professions education, and biomedical research, typically affiliated with a university.
-
E.
medical campus
A medical campus is a dedicated complex that integrates healthcare facilities, educational institutions, research centers, and support services within a unified environment focused on medical care and advancement.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:52 p.m.