Triple
T28712720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikimedia fundraising infrastructure |
E729869
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fundraising technology stack |
C55206
|
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: fundraising technology stack Context triple: [Wikimedia fundraising infrastructure, instanceOf, fundraising technology stack]
-
A.
fundraiser
A fundraiser is an event, campaign, or individual effort designed to solicit voluntary financial contributions or resources to support a specific cause, organization, or project.
-
B.
fundraising expert
A fundraising expert is a professional who strategically plans, manages, and optimizes campaigns and donor relationships to secure financial support for organizations or causes.
-
C.
grantmaking foundation network
A grantmaking foundation network is a collaborative association of philanthropic organizations that coordinate strategies, share knowledge, and sometimes pool resources to more effectively fund and advance shared social, cultural, or environmental goals.
-
D.
humanitarian financial reporting platform
A humanitarian financial reporting platform is a digital system that tracks, analyzes, and transparently reports the flow and impact of funds dedicated to humanitarian projects and emergency responses.
-
E.
portfolio of funded organisations
A portfolio of funded organisations is a curated collection of entities that have received financial investment or support, managed and monitored together to track performance, impact, and risk.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:49 a.m.