Triple
T28503977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFE Flank Agreement |
E721320
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms control protocol |
C44103
|
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 control protocol Context triple: [CFE Flank Agreement, instanceOf, arms control protocol]
-
A.
arms control regime
chosen
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.
-
B.
arms limitation conference
An arms limitation conference is a formal international meeting where representatives of states negotiate agreements to restrict, reduce, or regulate the development, stockpiling, and deployment of weapons.
-
C.
arms control advocate
An arms control advocate is an individual who actively promotes the limitation, reduction, and responsible regulation of weapons and military capabilities to enhance global security and prevent conflict.
-
D.
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.
-
E.
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.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:08 a.m.