Triple
T16342450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO City of Gastronomy |
E396840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO Creative City designation |
C21866
|
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 Creative City designation Context triple: [UNESCO City of Gastronomy, instanceOf, UNESCO Creative City designation]
-
A.
UNESCO distinction
chosen
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.
-
B.
UNESCO register
A UNESCO register is an official list maintained by UNESCO that records and recognizes sites, practices, or items of outstanding cultural or natural significance for protection and preservation.
-
C.
UNESCO international day
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.
-
D.
UNESCO declaration
A UNESCO declaration is a formal, non-binding instrument adopted by UNESCO’s governing bodies that sets out shared principles, standards, or commitments on cultural, educational, scientific, or ethical issues to guide member states and the international community.
-
E.
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.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:07 a.m.