Triple
T9672850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention of Belém do Pará |
E234071
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty on violence against women |
C566
|
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: treaty on violence against women Context triple: [Convention of Belém do Pará, instanceOf, treaty on violence against women]
-
A.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
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.
-
C.
World Health Organization treaty
A World Health Organization treaty is a formal, legally binding international agreement negotiated under the auspices of the WHO to coordinate and regulate global health policies, standards, and responses among member states.
-
D.
network of national human rights institutions
A network of national human rights institutions is a coordinated system of independent, state-based bodies that collaborate to promote, protect, and strengthen human rights standards and practices domestically and internationally.
-
E.
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.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:15 p.m.