Triple
T9984386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health Sciences Building |
E196530
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health sciences facility |
C4715
|
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: health sciences facility Context triple: [Health Sciences Building, instanceOf, health sciences facility]
-
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.
medical campus
chosen
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.
-
C.
hospital system facilities
A hospital system facilities class represents the physical infrastructure, equipment, and support services that enable the delivery of healthcare across one or more hospital locations.
-
D.
health sciences school
A health sciences school is an educational institution that offers specialized programs and training in fields such as medicine, nursing, public health, and allied health professions to prepare students for careers in healthcare and biomedical research.
-
E.
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.
- 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_69ca82efbce081908179b4b9c65096eb |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:49 p.m.