Triple
T36836536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partnership2Gether |
E910286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community partnership initiative |
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 partnership initiative Context triple: [Partnership2Gether, instanceOf, community partnership initiative]
-
A.
community-based partnership
chosen
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.
-
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-driven initiative
A community-driven initiative is a collaborative effort led and shaped by local stakeholders who identify needs, design solutions, and take collective action to improve their shared environment or well-being.
-
D.
community engagement campaign
A community engagement campaign is a coordinated set of activities and communications designed to inform, involve, and motivate community members to participate in achieving a shared goal or addressing a common issue.
-
E.
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.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.