Triple

T36711808
Position Surface form Disambiguated ID Type / Status
Subject General Security of Military Information Agreement (GSOMIA) E906812 entity
Predicate instanceOf P0 FINISHED
Object military information sharing agreement C65547 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: military information sharing agreement
Context triple: [General Security of Military Information Agreement (GSOMIA), instanceOf, military information sharing agreement]
  • A. 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.
  • B. military base agreement
    A military base agreement is a formal arrangement between a host nation and a foreign state that defines the rights, responsibilities, and conditions under which the foreign state may establish, operate, and maintain military facilities on the host nation’s territory.
  • C. federal information sharing initiative
    A federal information sharing initiative is a coordinated program through which federal agencies and authorized partners securely exchange data, intelligence, and best practices to improve decision-making, policy implementation, and national security.
  • D. multinational military forum
    A multinational military forum is an organized platform where representatives from multiple countries' armed forces convene to discuss security issues, coordinate policies, share best practices, and enhance mutual understanding and cooperation.
  • E. collective defense agreement
    A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
  • F. None of above. chosen

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_69f76e73ad108190a5241585f2303e9a completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:12 p.m.