Triple
T9918419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Training Mission-Afghanistan |
E185928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security sector reform mission |
C18876
|
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: security sector reform mission Context triple: [NATO Training Mission-Afghanistan, instanceOf, security sector reform mission]
-
A.
security sector reform advisory team
A security sector reform advisory team is a group of experts that supports governments and institutions in designing, implementing, and evaluating reforms to make security forces more effective, accountable, and aligned with democratic governance and human rights standards.
-
B.
security sector reform body
chosen
A security sector reform body is an organization or institutional mechanism responsible for planning, coordinating, and overseeing changes to a country’s security institutions—such as the military, police, and intelligence services—to make them more effective, accountable, and aligned with democratic norms and human rights.
-
C.
security initiative
A security initiative is a coordinated set of actions, policies, and resources designed to improve an organization’s protection against threats and vulnerabilities.
-
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.
security force
A security force is an organized group responsible for protecting people, property, and interests by preventing, detecting, and responding to threats or unlawful activities.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 8:42 p.m.