Triple
T20856554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Pacific Nuclear Free Zone |
E513495
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms control arrangement |
C17914
|
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 arrangement Context triple: [South Pacific Nuclear Free Zone, instanceOf, arms control arrangement]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
regional arms control norm
chosen
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.
disarmament body
A disarmament body is an organization or institutional entity responsible for negotiating, implementing, monitoring, or promoting the reduction, limitation, or elimination of weapons, particularly weapons of mass destruction.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:44 p.m.