Triple
T18991398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Argaum |
E464691
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | siege of Gawilghur |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: siege of Gawilghur | Statement: [Battle of Argaum, followedBy, siege of Gawilghur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: siege of Gawilghur Context triple: [Battle of Argaum, followedBy, siege of Gawilghur]
-
A.
Siege of Alamut
The Siege of Alamut was the 1256 Mongol assault that destroyed the Nizari Ismaili stronghold of Alamut Castle in northern Iran, effectively ending the power of the so‑called Assassins.
-
B.
Battle of Gawilghur
The Battle of Gawilghur was a 1803 engagement during the Second Anglo-Maratha War in which British forces stormed a formidable hill fortress in central India, significantly weakening Maratha resistance.
-
C.
Siege of Multan
The Siege of Multan was a pivotal 1848–1849 British East India Company military operation against Sikh forces in the fortified city of Multan, helping to bring about the collapse of the Sikh Empire in the Second Anglo-Sikh War.
-
D.
Siege of Samarkand
The Siege of Samarkand was a pivotal 1220 Mongol assault in Central Asia during Genghis Khan’s campaigns, resulting in the brutal capture and devastation of one of the Khwarezmian Empire’s major cities.
-
E.
Siege of Gurganj
The Siege of Gurganj was a brutal Mongol assault in 1221 on the wealthy Khwarazmian city of Gurganj, resulting in its destruction and marking a decisive step in the Mongol conquest of Central Asia.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: siege of Gawilghur Target entity description: The siege of Gawilghur was a 1803 British East India Company assault on the formidable hill fortress of Gawilghur during the Second Anglo-Maratha War, resulting in a decisive British victory over Maratha forces.
-
A.
Siege of Alamut
The Siege of Alamut was the 1256 Mongol assault that destroyed the Nizari Ismaili stronghold of Alamut Castle in northern Iran, effectively ending the power of the so‑called Assassins.
-
B.
Battle of Gawilghur
chosen
The Battle of Gawilghur was a 1803 engagement during the Second Anglo-Maratha War in which British forces stormed a formidable hill fortress in central India, significantly weakening Maratha resistance.
-
C.
Siege of Multan
The Siege of Multan was a pivotal 1848–1849 British East India Company military operation against Sikh forces in the fortified city of Multan, helping to bring about the collapse of the Sikh Empire in the Second Anglo-Sikh War.
-
D.
Siege of Samarkand
The Siege of Samarkand was a pivotal 1220 Mongol assault in Central Asia during Genghis Khan’s campaigns, resulting in the brutal capture and devastation of one of the Khwarezmian Empire’s major cities.
-
E.
Siege of Gurganj
The Siege of Gurganj was a brutal Mongol assault in 1221 on the wealthy Khwarazmian city of Gurganj, resulting in its destruction and marking a decisive step in the Mongol conquest of Central Asia.
- F. None of above.
Provenance (2 batches)
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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d67dee4c8190ac2017ff748ea6aa |
completed | April 20, 2026, 7:32 a.m. |
Created at: April 10, 2026, 12:01 p.m.