Triple

T4598078
Position Surface form Disambiguated ID Type / Status
Subject NATO Prague Summit 2002 decisions E100252 entity
Predicate instanceOf P0 FINISHED
Object NATO summit decision package C13819 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: NATO summit decision package
Context triple: [NATO Prague Summit 2002 decisions, instanceOf, NATO summit decision package]
  • A. NATO military position
    A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
  • B. post–Cold War settlement document
    A post–Cold War settlement document is a formal agreement or framework, typically involving states and international organizations, that redefines political, security, and economic arrangements in the aftermath of the Cold War’s bipolar order.
  • C. European Union security and defence policy instrument
    A European Union security and defence policy instrument is a formal mechanism, tool, or framework established by the EU to plan, coordinate, and implement collective actions in the fields of security, crisis management, and defence.
  • D. NATO capability chosen
    A NATO capability is a specific military, political, or logistical asset, function, or competence that member states collectively develop, maintain, and coordinate to fulfill the Alliance’s strategic objectives and operational requirements.
  • E. arms deal
    An arms deal is a transaction involving the sale, transfer, or exchange of weapons and military equipment between parties, often states, organizations, or private entities.
  • 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_69bd43cbc014819098b45f435908f88a completed March 20, 2026, 12:55 p.m.
Created at: March 20, 2026, 1:11 p.m.