Triple
T31902872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karachi Agreement of 1949 |
E814470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indo-Pakistani accord |
C16010
|
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: Indo-Pakistani accord Context triple: [Karachi Agreement of 1949, instanceOf, Indo-Pakistani accord]
-
A.
India–China agreement
An India–China agreement is a formal bilateral accord between the governments of India and China that outlines mutually accepted terms on specific political, economic, or security issues to manage relations and reduce conflict.
-
B.
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.
-
C.
non‑aggression pact
chosen
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.
Indo-Pakistani War
The Indo-Pakistani War is a military conflict between India and Pakistan, typically referring to one of several wars fought since 1947 over territorial, political, and ideological disputes, most notably concerning the Kashmir region.
-
E.
India–Russia military cooperation activity
India–Russia military cooperation activity encompasses the joint defense initiatives, arms trade, technology transfers, training exercises, and strategic collaborations undertaken between India and Russia to enhance their mutual security and military capabilities.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, midnight