Triple
T25306597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senior Nutrition Programs |
E634497
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-based service |
C21870
|
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 service Context triple: [Senior Nutrition Programs, instanceOf, community-based service]
-
A.
community-based program
chosen
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
-
B.
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.
-
C.
community organisation
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.
-
D.
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.
-
E.
community-based mechanism
A community-based mechanism is a locally driven process or structure through which community members collectively identify, decide on, and implement actions to address shared needs or manage common resources.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:25 p.m.