Triple

T10910765
Position Surface form Disambiguated ID Type / Status
Subject SADC Protocol on Politics, Defence and Security Cooperation E257690 entity
Predicate instanceOf P0 FINISHED
Object regional security protocol C20661 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: regional security protocol
Context triple: [SADC Protocol on Politics, Defence and Security Cooperation, instanceOf, regional security protocol]
  • A. regional economic integration protocol
    A regional economic integration protocol is a formal agreement among neighboring or closely linked countries that coordinates trade, investment, and regulatory policies to reduce barriers and promote a more unified regional market.
  • B. regional arms control norm
    A regional arms control norm is a shared expectation among states within a specific geographic area that guides and constrains their behavior regarding the development, deployment, and transfer of weapons to enhance stability and reduce the risk of conflict.
  • C. peace and security architecture chosen
    A peace and security architecture is an integrated system of institutions, norms, mechanisms, and processes designed to prevent conflict, manage crises, and sustain long-term stability within and among states.
  • D. security doctrine
    A security doctrine is a formalized set of principles and strategies that guides how a state or organization understands, prioritizes, and responds to threats to its security.
  • E. trilateral security partners
    Trilateral security partners are three sovereign entities that formally coordinate defense, intelligence, and strategic policies to enhance their collective security and regional or global stability.
  • 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_69d6aa864ed88190818280ab6791d065 completed April 8, 2026, 7:20 p.m.
Created at: April 8, 2026, 9:22 p.m.