Triple
T2005141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Health and Social Care (HSC) system |
E43563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated health and social care system |
C5895
|
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: integrated health and social care system Context triple: [Health and Social Care (HSC) system, instanceOf, integrated health and social care system]
-
A.
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.
-
B.
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.
-
C.
social system
chosen
A social system is an organized set of interrelated individuals, groups, institutions, and norms that interact in patterned ways to maintain and transform a society.
-
D.
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.
-
E.
health classification system
A health classification system is a structured framework used to categorize and code health-related conditions, statuses, and services for consistent recording, analysis, and decision-making.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.