Triple
T3958867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Secretary-General’s Special Advocate for Inclusive Finance for Development |
E85851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-level UN advocacy position |
C14270
|
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: high-level UN advocacy position Context triple: [United Nations Secretary-General’s Special Advocate for Inclusive Finance for Development, instanceOf, high-level UN advocacy position]
-
A.
senior United Nations position
chosen
A senior United Nations position is a high-level leadership role responsible for shaping and implementing UN policies, strategies, and operations across member states and agencies.
-
B.
advocacy unit
An advocacy unit is an organized group or department dedicated to influencing policies, decisions, or public opinion in support of specific causes or interests.
-
C.
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.
-
D.
mission to the United Nations
A mission to the United Nations is a permanent diplomatic representation of a member state or observer entity to the UN, responsible for managing its participation, negotiations, and interests within the organization.
-
E.
diplomatic position
A diplomatic position is an official role within a government or international organization responsible for managing and representing a state's or entity's interests in foreign relations and negotiations.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:31 p.m.