Triple
T1416796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War of the Sixth Coalition |
E31936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Napoleonic Wars campaign |
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: Napoleonic Wars campaign Context triple: [War of the Sixth Coalition, instanceOf, Napoleonic Wars campaign]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
military campaign phase
A military campaign phase is a distinct, time-bounded segment of a broader military operation characterized by specific objectives, actions, and resource allocations that contribute to the overall strategic goal.
-
E.
military campaign theater
A military campaign theater is a geographically defined area where coordinated military operations and strategies are conducted to achieve specific objectives within a broader conflict.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:59 p.m.