Triple
T31742421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahore Memorandum of Understanding |
E810176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear risk-reduction agreement |
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: nuclear risk-reduction agreement Context triple: [Lahore Memorandum of Understanding, instanceOf, nuclear risk-reduction agreement]
-
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.
nuclear reservation
A nuclear reservation is a designated area of land set aside for the development, testing, production, storage, or decommissioning of nuclear materials and facilities under strict regulatory control.
-
C.
non‑aggression pact
A non-aggression pact is a formal agreement between two or more parties in which they commit not to engage in military or hostile actions against each other, typically for a specified period.
-
D.
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.
-
E.
nuclear weapons program
A nuclear weapons program is an organized, often state-led effort to research, develop, test, produce, and maintain nuclear warheads and their delivery systems for military deterrence or potential use.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:25 p.m.