Triple
T1379811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHS Digital |
E29311
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health informatics organisation |
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 informatics organisation Context triple: [NHS Digital, instanceOf, health informatics organisation]
-
A.
medical organization
chosen
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
B.
healthcare accreditation organization
A healthcare accreditation organization is an independent body that evaluates and certifies healthcare providers and institutions against established quality and safety standards to ensure consistent, high-quality patient care.
-
C.
publicly funded healthcare organisation type
A publicly funded healthcare organisation type is an entity that delivers health services primarily financed through government revenues or compulsory public insurance, rather than direct private payments.
-
D.
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.
-
E.
global health institution
A global health institution is an organization that coordinates international efforts to prevent disease, promote health, and strengthen health systems across countries through research, policy, funding, and program implementation.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.