Triple
T30962548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHS ambulance services in England |
E788867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public healthcare service |
C47270
|
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 healthcare service Context triple: [NHS ambulance services in England, instanceOf, public healthcare service]
-
A.
Healthcare service
chosen
A healthcare service is an organized set of medical and supportive activities provided by professionals and institutions to promote, maintain, or restore individuals’ health and well-being.
-
B.
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.
-
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.
public health system
A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
-
E.
health service support body
A health service support body is an organization or unit that provides administrative, logistical, technical, or advisory functions to enable and enhance the effective delivery of healthcare services.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:54 p.m.