Triple
T1118347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Trafalgar |
E11152
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the Napoleonic Wars |
C472
|
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: battle of the Napoleonic Wars Context triple: [Battle of Trafalgar, instanceOf, battle of the Napoleonic Wars]
-
A.
engagement of the French Revolutionary Wars
An engagement of the French Revolutionary Wars is a specific military clash—ranging from small skirmishes to major battles—fought between Revolutionary France and its opponents between 1792 and 1802.
-
B.
European war
chosen
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
C.
event in the Seven Years' War
An event in the Seven Years' War is a specific historical occurrence—such as a battle, treaty, campaign, or political decision—that took place between 1756 and 1763 and significantly influenced the course or outcome of the global conflict.
-
D.
Napoleonic policy
Napoleonic policy refers to the strategic, administrative, legal, and military measures implemented by Napoleon Bonaparte to centralize authority, modernize state institutions, expand French influence, and consolidate his personal rule across Europe.
-
E.
imperial war
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.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:43 p.m.