Triple
T311871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage Convention |
E7625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO convention |
C4069
|
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 convention Context triple: [UNESCO World Heritage Convention, instanceOf, UNESCO convention]
-
A.
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.
-
B.
article of an international treaty
An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
-
C.
international human rights instrument
An international human rights instrument is a formal, legally or politically binding document adopted by states or international organizations that defines, codifies, and promotes the protection of fundamental human rights and freedoms across national borders.
-
D.
UNESCO biosphere reserve
A UNESCO biosphere reserve is a designated area that promotes solutions reconciling the conservation of biodiversity with its sustainable use, integrating protected ecosystems, research, and local community development.
-
E.
international observance
An international observance is a designated day, week, year, or decade recognized by global or intergovernmental organizations to raise awareness, promote action, or commemorate significant issues, events, or causes across countries.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:07 p.m.