Triple
T31400145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khyber Pass operations |
E800974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Second Anglo-Afghan War campaign |
C60122
|
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: Second Anglo-Afghan War campaign Context triple: [Khyber Pass operations, instanceOf, Second Anglo-Afghan War campaign]
-
A.
Anglo-Afghan War
The Anglo-Afghan War refers to any of three 19th- and early 20th-century conflicts between the British Empire and Afghanistan, fought primarily over imperial influence and control in Central Asia.
-
B.
Mughal campaign
A Mughal campaign is a military expedition undertaken by the Mughal Empire to expand, consolidate, or defend its territories through organized warfare and strategic operations.
-
C.
event in the Second Anglo-Afghan War
chosen
An "event in the Second Anglo-Afghan War" is a specific historical occurrence—such as a battle, treaty, campaign, or political development—that took place between 1878 and 1880 in the context of the conflict between the British Empire and Afghanistan.
-
D.
Anglo-Maratha War
The Anglo-Maratha War refers to a series of three late 18th- and early 19th-century conflicts between the British East India Company and the Maratha Empire that ultimately led to British dominance over most of India.
-
E.
battle of the Second Boer War
A battle of the Second Boer War is a military engagement fought between British (and imperial) forces and Boer republic commandos in South Africa between 1899 and 1902, characterized by a mix of conventional and guerrilla warfare over control of territory and political sovereignty.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
Created at: April 29, 2026, 9:19 p.m.