Triple
T14025796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exercise Indra Navy |
E337452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | India–Russia military cooperation activity |
C33972
|
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: India–Russia military cooperation activity Context triple: [Exercise Indra Navy, instanceOf, India–Russia military cooperation activity]
-
A.
invasion of Russia
Invasion of Russia is a large-scale military campaign in which foreign forces attempt to penetrate, occupy, or subdue Russian territory, often facing vast distances, harsh climate, and strong defensive resistance.
-
B.
formation of the Russian Armed Forces
The formation of the Russian Armed Forces is the historical and organizational process through which Russia established, structured, and developed its modern military institutions, branches, and command systems following the dissolution of the Soviet Union.
-
C.
United States–Russia relations event
A United States–Russia relations event is a specific occurrence, interaction, or development that significantly affects the political, diplomatic, military, economic, or cultural relationship between the United States and Russia.
-
D.
arms deal
An arms deal is a transaction involving the sale, transfer, or exchange of weapons and military equipment between parties, often states, organizations, or private entities.
-
E.
settlement in Russia
A settlement in Russia is a populated locality, ranging from small rural communities to larger urban-type areas, officially recognized within the country’s administrative-territorial structure.
- F. None of above. chosen
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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:20 p.m.