Triple
T12591267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale Center for Immuno-Oncology |
E300608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | clinical research hub |
C29034
|
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 research hub Context triple: [Yale Center for Immuno-Oncology, instanceOf, clinical research hub]
-
A.
medical research centre
chosen
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.
-
B.
medical research collaboration
A medical research collaboration is a coordinated partnership among researchers, clinicians, institutions, and sometimes industry or patient groups to jointly design, conduct, and analyze studies that advance medical knowledge and improve health outcomes.
-
C.
multicenter clinical study
A multicenter clinical study is a coordinated research trial conducted simultaneously at multiple geographically distinct sites under a common protocol to evaluate the safety, efficacy, or outcomes of a medical intervention in a diverse patient population.
-
D.
research facility
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
-
E.
intramural research program
An intramural research program is an organized, institutionally funded initiative in which an organization’s own scientists conduct research on-site using internal facilities and resources.
- 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.