Triple

T29584818
Position Surface form Disambiguated ID Type / Status
Subject Transitional Charter of Ethiopia E753692 entity
Predicate instanceOf P0 FINISHED
Object transitional political agreement 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: transitional political agreement
Context triple: [Transitional Charter of Ethiopia, instanceOf, transitional political agreement]
  • A. 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.
  • 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. medieval political agreement
    A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
  • D. political transition
    A political transition is the process by which a political system, regime, or leadership changes from one form or ruling group to another, often involving shifts in institutions, power structures, and governance practices.
  • E. intergovernmental consensus
    Intergovernmental consensus is a collective agreement reached among multiple governments or states, typically through negotiation and compromise, that establishes a shared position or decision on a specific issue.
  • 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_69f0ef80bf8c8190ad286e99f7df0c63 completed April 28, 2026, 5:33 p.m.
Created at: April 28, 2026, 6:09 p.m.