Triple
T13755379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard Pilgrim Health Care |
E330462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health services organization |
C437
|
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 services organization Context triple: [Harvard Pilgrim Health Care, instanceOf, health services organization]
-
A.
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.
-
B.
medical organization
chosen
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
C.
healthcare administration service
A healthcare administration service manages the non-clinical operations of healthcare organizations, including scheduling, billing, compliance, records management, and coordination among providers, payers, and patients to ensure efficient and compliant delivery of care.
-
D.
health service purchaser
A health service purchaser is an entity (such as an insurer, government body, or employer) that buys or commissions healthcare services on behalf of a defined population, managing contracts, payments, and performance to ensure value and quality of care.
-
E.
health care organization type
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.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:09 p.m.