Triple

T1149581
Position Surface form Disambiguated ID Type / Status
Subject Protocol of Managua E23644 entity
Predicate instanceOf P0 FINISHED
Object treaty amending the Charter of the Organization of American States C4085 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: treaty amending the Charter of the Organization of American States
Context triple: [Protocol of Managua, instanceOf, treaty amending the Charter of the Organization of American States]
  • A. treaty amendment chosen
    A treaty amendment is a formal, negotiated change to an existing international agreement that modifies, adds to, or removes specific obligations or provisions for its parties.
  • B. amendments to international treaty
    Amendments to international treaty: formal, negotiated changes or additions agreed upon by the treaty parties that modify, clarify, or expand the original treaty’s provisions and obligations.
  • C. treaty
    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. organ of the Organization of American States
    An organ of the Organization of American States is an official institutional body established by the OAS Charter to perform specific functions—such as political, judicial, administrative, or advisory roles—in support of the organization’s purposes and decision-making processes.
  • E. article of an international treaty
    An article of an international treaty is a distinct, numbered provision that sets out specific rights, obligations, definitions, or procedures agreed upon by the treaty’s parties.
  • 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_69a493f0d32c8190ac74bad3c87f2641 completed March 1, 2026, 7:30 p.m.
Created at: March 1, 2026, 7:44 p.m.