Triple
T38323900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aide-Mémoire on Arms Management in Nepal |
E1036729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms management framework |
C64372
|
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: arms management framework Context triple: [Aide-Mémoire on Arms Management in Nepal, instanceOf, arms management framework]
-
A.
arms transfer mechanism
An arms transfer mechanism is a system or process that facilitates the legal or illegal movement, sale, or provision of weapons and related military equipment between parties, such as states, organizations, or individuals.
-
B.
arms control program
chosen
An arms control program is an organized set of policies, agreements, and verification measures designed to limit, reduce, or regulate the development, stockpiling, and use of weapons to enhance security and stability.
-
C.
command-and-control framework
A command-and-control framework is a structured system that enables centralized coordination, tasking, and monitoring of distributed agents or components, often used to manage operations, automation, or cyber activities.
-
D.
arms control regime
An arms control regime is a set of formal and informal agreements, institutions, and practices through which states collectively regulate the development, possession, and use of weapons to enhance security and stability.
-
E.
operational arm
An operational arm is a functional extension or division of an organization responsible for executing day-to-day activities and implementing strategic decisions.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.