Triple
T2558498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations working groups |
E56784
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations body type |
C6042
|
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: United Nations body type Context triple: [United Nations working groups, instanceOf, United Nations body type]
-
A.
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.
-
B.
United Nations specialized body
chosen
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.
-
C.
United Nations facility
A United Nations facility is a physical site, such as a headquarters, office, base, or specialized center, that is owned, leased, or operated by the UN to support its diplomatic, administrative, peacekeeping, humanitarian, or development activities.
-
D.
United Nations role
The "United Nations role" conceptual class represents the specific function, responsibility, or position an entity holds within the UN system, such as mediator, peacekeeper, observer, or member state.
-
E.
World Health Organization body
A World Health Organization body is an organizational unit within the WHO responsible for specific global health functions such as policy-making, standard-setting, coordination, or technical support to member states.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.