Triple
T1700793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAB National Committees |
E36762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNESCO-related body |
C4250
|
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 body Context triple: [MAB National Committees, instanceOf, UNESCO-related body]
-
A.
UNESCO advisory body
chosen
A UNESCO advisory body is an expert committee or organization that provides specialized guidance, evaluations, and recommendations to UNESCO to inform its decisions, policies, and program implementation in specific fields such as culture, education, science, or heritage.
-
B.
principal organ of UNESCO
The principal organ of UNESCO is a primary governing body responsible for setting the organization’s policies, strategic direction, and overall programmatic priorities.
-
C.
UNESCO regional committee
A UNESCO regional committee is a governance body that coordinates, advises, and implements UNESCO’s programs and policies within a specific geographic region, facilitating cooperation among member states and regional partners.
-
D.
United Nations specialized body
A United Nations specialized body is an autonomous international organization linked to the UN through formal agreements, collaborating on specific global issues such as health, labor, or education while maintaining its own governance and budget.
-
E.
UN administrative body
A UN administrative body is an organizational entity within the United Nations responsible for managing, coordinating, and implementing the day-to-day operations, policies, and programs mandated by UN organs and agreements.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:30 p.m.