Triple

T37786291
Position Surface form Disambiguated ID Type / Status
Subject CIS Joint Command E941963 entity
Predicate instanceOf P0 FINISHED
Object peacekeeping command C1802 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: peacekeeping command
Context triple: [CIS Joint Command, instanceOf, peacekeeping command]
  • A. peacekeeping area of operations
    A peacekeeping area of operations is the geographically defined space within which peacekeeping forces are authorized and tasked to conduct missions, maintain security, and support the implementation of peace agreements.
  • B. peacekeeping force chosen
    A peacekeeping force is an organized, often multinational group deployed to conflict or post-conflict areas to monitor ceasefires, support political processes, protect civilians, and help maintain or restore peace and security.
  • C. peacekeeping mandate
    A peacekeeping mandate is an official authorization, typically issued by an international body like the United Nations, that defines the scope, objectives, rules of engagement, and duration of a peacekeeping operation in a conflict or post-conflict setting.
  • D. peace enforcement mission
    A peace enforcement mission is a military or multinational operation authorized to use coercive measures, including force, to compel compliance with international mandates and restore or maintain peace in a conflict area.
  • E. peacekeeping doctrine
    Peacekeeping doctrine is a conceptual framework that outlines the principles, strategies, and operational guidelines for the deployment and conduct of forces to prevent, contain, or resolve armed conflict while supporting long-term stability and political processes.
  • 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_69f76ee5cb0c81909a363d1c929156c0 completed May 3, 2026, 3:51 p.m.
Created at: May 3, 2026, 4:19 p.m.