Triple
T1968315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Rights Committee |
E42739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations treaty body |
C2067
|
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: United Nations treaty body Context triple: [Human Rights Committee, instanceOf, United Nations treaty body]
-
A.
United Nations specialized body
A United Nations specialized body is an autonomous international organization linked to the UN through formal agreements, collaborating on specific global issues such as health, labor, or education while maintaining its own governance and budget.
-
B.
intergovernmental legal body
chosen
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
C.
United Nations specialized institution
A United Nations specialized institution is an autonomous intergovernmental organization, linked to the UN through formal agreements, that coordinates international cooperation in a specific field such as health, labor, or education.
-
D.
UN administrative body
A UN administrative body is an organizational entity within the United Nations responsible for managing, coordinating, and implementing the day-to-day operations, policies, and programs mandated by UN organs and agreements.
-
E.
party to an international treaty
A party to an international treaty is a state or international organization that has formally consented to be bound by the treaty’s terms in accordance with international law.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.