Triple
T33691310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kent Community Health NHS Foundation Trust |
E863188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community health provider |
C31723
|
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: community health provider Context triple: [Kent Community Health NHS Foundation Trust, instanceOf, community health provider]
-
A.
community health center
A community health center is a local, patient-centered facility that provides accessible, comprehensive primary and preventive healthcare services, often focusing on underserved populations regardless of their ability to pay.
-
B.
community health specialist
A community health specialist plans, implements, and evaluates programs and interventions to improve the health and well-being of specific populations by addressing medical, social, and environmental factors.
-
C.
clinical care provider
A clinical care provider is a trained healthcare professional who assesses, diagnoses, treats, and manages patients’ health needs in clinical settings.
-
D.
healthcare services provider
chosen
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.
public health partnership
A public health partnership is a collaborative alliance among governmental agencies, community organizations, healthcare providers, and other stakeholders that coordinates resources and efforts to improve population health outcomes and address public health challenges.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.