Triple
T2801824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Anglo-Mysore War |
E53164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglo-Mysore War |
C2457
|
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: Anglo-Mysore War Context triple: [Fourth Anglo-Mysore War, instanceOf, Anglo-Mysore War]
-
A.
battle of the Second Anglo-Dutch War
A battle of the Second Anglo-Dutch War is a specific naval or amphibious military engagement fought between English and Dutch forces between 1665 and 1667 as part of their broader conflict over maritime trade and colonial dominance.
-
B.
battle of the Second Anglo-Dutch War
A battle of the Second Anglo-Dutch War is a specific naval or amphibious military engagement fought between English and Dutch forces between 1665 and 1667 as part of their broader conflict for maritime and commercial supremacy.
-
C.
battle of the Franco-Dutch War
A battle of the Franco-Dutch War is a military engagement fought between 1672 and 1678 involving France and its allies against the Dutch Republic and its shifting coalition of European powers, typically characterized by complex political motives and evolving alliances.
-
D.
imperial war
chosen
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
-
E.
succession war
A succession war is an armed conflict triggered by competing claims to a throne or leadership position, typically following the death, deposition, or disputed legitimacy of a ruler.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:58 p.m.