Triple
T27672486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms Trade Treaty |
E697697
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international arms control agreement |
C824
|
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: international arms control agreement Context triple: [Arms Trade Treaty, instanceOf, international arms control agreement]
-
A.
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.
-
B.
international agreement
chosen
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
C.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
-
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 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.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:42 p.m.