Triple
T27727843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Day for Tolerance |
E697350
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO-related observance |
C21808
|
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: UNESCO-related observance Context triple: [International Day for Tolerance, instanceOf, UNESCO-related observance]
-
A.
UNESCO international day
chosen
A UNESCO international day is a globally recognized observance established by UNESCO to raise awareness, promote advocacy, and mobilize action around specific themes related to education, culture, science, and human rights.
-
B.
United Nations observance
A United Nations observance is an officially designated day, week, year, or decade established by the UN to raise awareness, mobilize action, and promote international norms around specific global issues or themes.
-
C.
UNESCO campaign
A UNESCO campaign is a coordinated global initiative led or endorsed by UNESCO to promote awareness, advocacy, and action around education, science, culture, or communication-related issues in line with its mandate.
-
D.
UNESCO programme
A UNESCO programme is an organized, often multi-year initiative led or coordinated by UNESCO to advance its mandate in education, science, culture, communication, or heritage through specific projects, partnerships, and policies.
-
E.
UNESCO distinction
A UNESCO distinction is an official recognition or designation granted by UNESCO to sites, practices, or entities that exemplify outstanding cultural, natural, educational, or scientific value in line with its global mission.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3:10 p.m.