Triple
T25130728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Research Data Alliance |
E629515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-driven initiative |
C49764
|
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-driven initiative Context triple: [Research Data Alliance, instanceOf, community-driven initiative]
-
A.
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.
-
B.
online initiative
An online initiative is a coordinated, internet-based effort or program designed to achieve a specific goal, such as raising awareness, driving engagement, or delivering services digitally.
-
C.
community development program
A community development program is an organized initiative designed to improve the social, economic, and environmental well-being of a specific community through collaborative planning, resource mobilization, and capacity-building activities.
-
D.
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.
-
E.
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.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:28 a.m.