Triple
T26265244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter Hospital Thane |
E656962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tertiary care hospital |
C21239
|
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: Tertiary care hospital Context triple: [Jupiter Hospital Thane, instanceOf, Tertiary care hospital]
-
A.
tertiary care center
chosen
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.
-
B.
teaching hospital
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.
-
C.
regional hospital system
A regional hospital system is an organized network of hospitals and related healthcare facilities within a specific geographic area that coordinates services, resources, and administration to provide comprehensive medical care to the local population.
-
D.
specialty medical center
A specialty medical center is a healthcare facility focused on diagnosing, treating, and managing conditions within a specific medical field or group of related specialties, often offering advanced expertise and technology.
-
E.
public hospital network
A public hospital network is a coordinated system of government-funded hospitals and healthcare facilities that collaboratively provide accessible, often low-cost or free, medical services to a defined population or region.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
Created at: April 26, 2026, 9:11 p.m.