Triple
T17140100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Development Assistance Committee |
E415940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | donor coordination forum |
C14661
|
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: donor coordination forum Context triple: [Development Assistance Committee, instanceOf, donor coordination forum]
-
A.
cooperative organizer
A cooperative organizer is an individual or system that coordinates people, resources, and processes to collaboratively plan, manage, and execute shared goals within a cooperative structure.
-
B.
coordination office
chosen
A coordination office is an organizational unit responsible for planning, aligning, and overseeing activities, resources, and communication among different stakeholders to ensure smooth and efficient execution of projects or operations.
-
C.
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.
-
D.
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.
-
E.
international non-governmental organization platform
An international non-governmental organization platform is a global, non-state entity that facilitates coordination, collaboration, and resource-sharing among NGOs across countries to address transnational social, environmental, or humanitarian issues.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:36 a.m.