Triple
T1125291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN Intergovernmental Commission on Human Rights |
E24705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ASEAN body |
C655
|
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: ASEAN body Context triple: [ASEAN Intergovernmental Commission on Human Rights, instanceOf, ASEAN body]
-
A.
Polynesian regional body
A Polynesian regional body is an organization that brings together Polynesian states and territories to coordinate on shared cultural, political, economic, and environmental interests across the Polynesian region.
-
B.
country in Southeast Asia
A country in Southeast Asia is a sovereign nation located in the southeastern region of the Asian continent, typically characterized by tropical climates, diverse cultures, and membership in regional organizations such as ASEAN.
-
C.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
D.
pan-African organization
A pan-African organization is an entity that promotes political, economic, social, and cultural cooperation and unity among African countries and peoples across the continent and diaspora.
-
E.
European Union body
A European Union body is an institution, agency, or other organizational entity established by the EU’s founding treaties or secondary legislation to perform specific political, regulatory, advisory, or administrative functions within the Union’s governance framework.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:44 p.m.