Triple
T37818208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit health care institutions |
E942834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health care organization category |
C15226
|
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 care organization category Context triple: [Jesuit health care institutions, instanceOf, health care organization category]
-
A.
health care organization type
chosen
A health care organization type is a category that classifies organizations based on their structure, services, and role in delivering, financing, or coordinating health care.
-
B.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
C.
healthcare organization unit
A healthcare organization unit is a distinct administrative or functional division within a healthcare system (such as a department, clinic, or ward) that delivers specific health-related services, manages resources, and supports patient care processes.
-
D.
healthcare services provider
A healthcare services provider is an organization or individual that delivers medical, therapeutic, or preventive health services to patients to diagnose, treat, and manage health conditions.
-
E.
health informatics organization
A health informatics organization is an entity that develops, manages, and applies information systems and data standards to improve the collection, exchange, analysis, and use of health information for clinical, administrative, and public health purposes.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.