Triple
T5801432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gender, Peace and Security Team |
E128630
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | gender mainstreaming mechanism |
C18893
|
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: gender mainstreaming mechanism Context triple: [Gender, Peace and Security Team, instanceOf, gender mainstreaming mechanism]
-
A.
women’s rights framework
A women’s rights framework is a conceptual and legal structure that identifies, protects, and advances the political, economic, social, and bodily rights of women and girls, addressing both formal equality and systemic gender-based discrimination.
-
B.
gender equality case
A gender equality case is a legal or administrative proceeding that addresses alleged discrimination, unequal treatment, or systemic bias based on gender, seeking to enforce or clarify rights to equal opportunities and protections.
-
C.
women’s affairs agency
A women’s affairs agency is a governmental or organizational body dedicated to promoting gender equality, protecting women’s rights, and advancing women’s social, economic, and political empowerment.
-
D.
gender minority
A gender minority is an individual or group whose gender identity, expression, or experience differs from the dominant or majority gender norms within a given society.
-
E.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.