Triple

T4088971
Position Surface form Disambiguated ID Type / Status
Subject Joint Comprehensive Plan of Action E87659 entity
Predicate instanceOf P0 FINISHED
Object multilateral treaty-level political agreement C824 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: multilateral treaty-level political agreement
Context triple: [Joint Comprehensive Plan of Action, instanceOf, multilateral treaty-level political agreement]
  • A. international agreement chosen
    An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
  • B. 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.
  • C. treaty-based alliance
    A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
  • D. 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.
  • E. party to an international treaty
    A party to an international treaty is a state or international organization that has formally consented to be bound by the treaty’s terms in accordance with international law.
  • 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_69aed94425148190be337845d56fac22 completed March 9, 2026, 2:29 p.m.
Created at: March 9, 2026, 3:39 p.m.