Triple

T23973395
Position Surface form Disambiguated ID Type / Status
Subject START II E604296 entity
Predicate instanceOf P0 FINISHED
Object strategic arms limitation agreement C44103 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: strategic arms limitation agreement
Context triple: [START II, instanceOf, strategic arms limitation agreement]
  • A. arms control regime chosen
    An arms control regime is a set of formal and informal agreements, institutions, and practices through which states collectively regulate the development, possession, and use of weapons to enhance security and stability.
  • B. arms limitation conference
    An arms limitation conference is a formal international meeting where representatives of states negotiate agreements to restrict, reduce, or regulate the development, stockpiling, and deployment of weapons.
  • C. Cold War–era treaty
    A Cold War–era treaty is a formal international agreement, typically between rival blocs or superpowers, designed to manage ideological conflict, arms competition, and spheres of influence during the mid-20th-century geopolitical standoff.
  • D. bilateral military agreement
    A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
  • 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_69e29543019c8190872462e593cc50b4 completed April 17, 2026, 8:17 p.m.
Created at: April 17, 2026, 9:25 p.m.