Triple
T16755518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Naval Conference |
E407197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | arms control conference |
C69
|
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 conference Context triple: [Washington Naval Conference, instanceOf, arms control conference]
-
A.
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.
-
B.
anti-war conference
An anti-war conference is a gathering of individuals, organizations, and experts dedicated to discussing, organizing, and promoting strategies for preventing war and advancing peace.
-
C.
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.
-
D.
diplomatic conference
chosen
A diplomatic conference is a formal gathering of representatives from different states or international organizations convened to negotiate agreements, resolve disputes, or discuss issues of mutual concern.
-
E.
nuclear weapons crisis
A nuclear weapons crisis is a high-stakes international confrontation in which the use or threatened use of nuclear arms becomes a realistic possibility, creating urgent risks of catastrophic escalation and intense diplomatic, military, and political pressure to resolve the conflict.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.