Triple
T8616556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ulm |
E204053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Napoleonic battle |
C15172
|
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 battle Context triple: [Battle of Ulm, instanceOf, Napoleonic battle]
-
A.
Engagement of the War of the Fifth Coalition
An Engagement of the War of the Fifth Coalition is a specific military action, battle, or campaign fought between the coalition powers (primarily Austria and its allies) and Napoleonic France and its allies during the 1809 conflict known as the War of the Fifth Coalition.
-
B.
battle of the Franco-Prussian War
A battle of the Franco-Prussian War is a specific military engagement between French and Prussian (and allied German) forces during the 1870–1871 conflict, characterized by defined participants, location, date, tactics, and outcome.
-
C.
civil war battle
A civil war battle is an armed conflict between organized factions within the same country, typically involving large-scale military engagements over political, territorial, or ideological control.
-
D.
episode of the Napoleonic Wars
chosen
An episode of the Napoleonic Wars is a distinct event, campaign, battle, or political development that forms part of the broader series of conflicts involving Napoleon Bonaparte’s French Empire and its adversaries between 1799 and 1815.
-
E.
battles
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:25 p.m.