Triple
T35087212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chemical Weapons Convention Review Conferences |
E1012608
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty review mechanism |
C63331
|
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 review mechanism Context triple: [Chemical Weapons Convention Review Conferences, instanceOf, treaty review mechanism]
-
A.
treaty practice
Treaty practice is the body of procedures, behaviors, and interpretive approaches that states and international actors consistently follow in negotiating, applying, and understanding treaties.
-
B.
treaty
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.
-
C.
treaty body resolution
A treaty body resolution is a formal decision or recommendation adopted by an international treaty-monitoring body that interprets, applies, or guides implementation of the provisions of a specific treaty.
-
D.
treaty system
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
E.
United Nations human rights review mechanism
A United Nations human rights review mechanism is a formal, periodic process through which UN bodies assess and monitor states’ compliance with international human rights obligations, typically involving state reports, independent expert or peer review, and public recommendations for improvement.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.