Triple
T11022300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Morgarten |
E260519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swiss military history event |
C8259
|
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: Swiss military history event Context triple: [Battle of Morgarten, instanceOf, Swiss military history event]
-
A.
Polish military history event
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
-
B.
event in the Franco-Prussian War
A specific occurrence or series of actions during the Franco-Prussian War that involved identifiable participants, took place at a particular time and location, and had notable military, political, or social consequences.
-
C.
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.
-
D.
military event
chosen
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
-
E.
European war
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.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.