Triple
T23946891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matignon Accords process |
E602936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomy agreement process |
C964
|
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: autonomy agreement process Context triple: [Matignon Accords process, instanceOf, autonomy agreement process]
-
A.
NATO process
A NATO process is a structured, collaborative decision-making and operational framework used by the North Atlantic Treaty Organization to plan, coordinate, and execute collective defense and security activities among its member states.
-
B.
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.
-
C.
self-determination policy
A self-determination policy is a framework of rules and practices that enables individuals or groups to autonomously make and implement decisions about their own political, social, or personal affairs without external coercion.
-
D.
political agreement
chosen
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
E.
self-determination legislation
Self-determination legislation comprises laws and legal frameworks that recognize, protect, and regulate the right of peoples or groups to autonomously determine their political status, governance, and development.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:16 p.m.