Triple
T12591040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale Center for Genomic Health |
E300603
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | clinical center |
C16785
|
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: clinical center Context triple: [Yale Center for Genomic Health, instanceOf, clinical center]
-
A.
academic medical center unit
An academic medical center unit is a specialized organizational subdivision within a teaching hospital or academic health system that integrates patient care, medical education, and research in a specific clinical or administrative domain.
-
B.
medical research centre
A medical research centre is an institution dedicated to conducting scientific studies and clinical investigations to advance knowledge, diagnosis, treatment, and prevention of diseases and health conditions.
-
C.
academic health sciences center
chosen
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.
-
D.
tertiary care center
A tertiary care center is a specialized healthcare facility that provides advanced, highly specialized diagnostic, therapeutic, and surgical services typically unavailable at primary or secondary care institutions.
-
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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:07 p.m.