Triple
T24737154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter on the Transfer of Sovereignty to Indonesia |
E618446
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | decolonization agreement |
C566
|
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 agreement Context triple: [Charter on the Transfer of Sovereignty to Indonesia, instanceOf, decolonization agreement]
-
A.
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.
-
B.
decolonization event
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.
-
C.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
D.
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.
-
E.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:03 a.m.