Triple
T34894360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internal autonomy agreements (1955) |
E1006389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | decolonization accord |
C16703
|
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: decolonization accord Context triple: [Internal autonomy agreements (1955), instanceOf, decolonization accord]
-
A.
decolonization event
chosen
A decolonization event is a historical or contemporary process in which a colonized territory or people dismantles colonial structures and asserts political, cultural, and economic self-determination.
-
B.
decolonization framework
A decolonization framework is a conceptual approach that identifies, critiques, and transforms colonial power structures, narratives, and practices in order to restore autonomy, knowledge systems, and agency to historically colonized peoples.
-
C.
Sudanese political agreement
A Sudanese political agreement is a formal accord between Sudanese political actors or factions that outlines shared principles, power arrangements, and mechanisms for governance, conflict resolution, or transition.
-
D.
constitutional accord
A constitutional accord is a formal agreement among key political actors or jurisdictions that defines, revises, or clarifies the fundamental rules, powers, and structures of a constitutional system.
-
E.
post–Cold War settlement document
A post–Cold War settlement document is a formal agreement or framework, typically involving states and international organizations, that redefines political, security, and economic arrangements in the aftermath of the Cold War’s bipolar order.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.