Triple
T337107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations treaty bodies |
E6752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human rights monitoring mechanism |
C3140
|
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: human rights monitoring mechanism Context triple: [United Nations treaty bodies, instanceOf, human rights monitoring mechanism]
-
A.
international human rights instrument
An international human rights instrument is a formal, legally or politically binding document adopted by states or international organizations that defines, codifies, and promotes the protection of fundamental human rights and freedoms across national borders.
-
B.
intelligence oversight committee
An intelligence oversight committee is a formal body responsible for monitoring, reviewing, and regulating the activities of intelligence agencies to ensure legality, accountability, and alignment with democratic norms and national interests.
-
C.
international observance
An international observance is a designated day, week, year, or decade recognized by global or intergovernmental organizations to raise awareness, promote action, or commemorate significant issues, events, or causes across countries.
-
D.
human
A human is a highly intelligent, social, and self-aware primate species capable of complex language, abstract reasoning, and cultural development.
-
E.
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.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.