Triple
T217388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter-American Commission on Human Rights |
E4136
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional human rights body |
C280
|
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: regional human rights body Context triple: [Inter-American Commission on Human Rights, instanceOf, regional human rights body]
-
A.
regional forum
A regional forum is a structured platform where stakeholders from a specific geographic area gather to discuss, coordinate, and address shared issues, policies, and development priorities.
-
B.
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.
-
C.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
D.
intergovernmental organization
chosen
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
E.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.