Triple
T19180093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manx Care |
E469548
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public health and social care provider |
C16263
|
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: public health and social care provider Context triple: [Manx Care, instanceOf, public health and social care provider]
-
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.
health and social care participation structure
A health and social care participation structure is an organized framework of roles, processes, and mechanisms that enable individuals, families, and communities to actively engage in planning, delivering, and evaluating integrated health and social care services.
-
C.
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.
-
D.
clinical care provider
A clinical care provider is a trained healthcare professional who assesses, diagnoses, treats, and manages patients’ health needs in clinical settings.
-
E.
public health organisation
chosen
A public health organisation is an entity, typically governmental or non-profit, that plans, implements, and evaluates programs and policies to protect and improve the health of populations.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:07 p.m.