Triple
T24622613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Living Cully collaborative |
E609452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-based partnership |
C48523
|
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 partnership Context triple: [Living Cully collaborative, instanceOf, community-based partnership]
-
A.
community-based program
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 engagement initiative
A community engagement initiative is a coordinated effort designed to actively involve local stakeholders in collaborative activities, decision-making, and problem-solving to improve shared social, cultural, or environmental outcomes.
-
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-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.
-
E.
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.
- F. None of above. chosen
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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:32 a.m.