Triple
T27529001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AHS |
E694916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-based health organization |
C20591
|
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-based health organization Context triple: [AHS, instanceOf, community-based health organization]
-
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 organisation
chosen
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
-
C.
community-based partnership
A community-based partnership is a collaborative relationship between local organizations, residents, and stakeholders who share resources, decision-making, and responsibilities to address community needs and achieve mutually beneficial goals.
-
D.
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.
-
E.
humanitarian health organization
A humanitarian health organization is an entity that delivers medical care, public health services, and health-related support to vulnerable or crisis-affected populations, prioritizing equity, neutrality, and rapid response to human suffering.
- 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:25 p.m.