Triple
T15183126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahey Hospital and Medical Center |
E362798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multispecialty medical center |
C93
|
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: multispecialty medical center Context triple: [Lahey Hospital and Medical Center, instanceOf, multispecialty medical center]
-
A.
medical district
A medical district is a designated urban area where healthcare facilities, such as hospitals, clinics, research centers, and related services, are concentrated to provide comprehensive medical care and support.
-
B.
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.
-
C.
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.
-
D.
teaching hospital
chosen
A teaching hospital is a medical facility that provides patient care while simultaneously serving as a training and research center for medical students, residents, and other healthcare professionals, typically in affiliation with a medical school.
-
E.
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.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:09 a.m.