Triple
T25376988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Union decisions on migration |
E633082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional intergovernmental decision |
C50079
|
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 intergovernmental decision Context triple: [African Union decisions on migration, instanceOf, regional intergovernmental decision]
-
A.
interregional relations
Interregional relations are the political, economic, social, and cultural interactions and institutionalized connections that occur between distinct geographic regions within or across states.
-
B.
regional politics
Regional politics is the study and practice of how political power, policies, and relationships operate within and between specific geographic areas or subnational units, such as states, provinces, or regions.
-
C.
regional institutional system
A regional institutional system is a coordinated network of organizations, rules, and practices within a specific geographic area that collectively shape governance, economic activity, and social outcomes.
-
D.
regional ministerial meeting
A regional ministerial meeting is a formal gathering of government ministers from countries within a specific geographic area to discuss, coordinate, and decide on shared policy issues and cooperative initiatives.
-
E.
regional assembly
A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:38 p.m.