Triple
T33267326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Humanitarian Day 2012 campaign |
E851686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global awareness campaign |
C59359
|
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: global awareness campaign Context triple: [World Humanitarian Day 2012 campaign, instanceOf, global awareness campaign]
-
A.
UN awareness campaign
A UN awareness campaign is a coordinated communication effort led or endorsed by the United Nations to inform, educate, and mobilize the public or specific stakeholders around global issues, UN initiatives, or international norms and goals.
-
B.
global initiative
A global initiative is a coordinated, large-scale effort involving multiple countries or international organizations aimed at addressing worldwide challenges or achieving shared global objectives.
-
C.
global conservation initiative
A global conservation initiative is a coordinated, international effort that unites governments, organizations, and communities to protect biodiversity, restore ecosystems, and promote sustainable use of natural resources worldwide.
-
D.
global action plan
A global action plan is a coordinated, strategic framework that outlines shared goals, responsibilities, timelines, and resources for addressing worldwide challenges across nations and organizations.
-
E.
environmental campaign
An environmental campaign is a coordinated set of actions and communications designed to raise awareness, influence behavior, and drive policy or social change to protect and improve the natural environment.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.