Triple
T2337097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitwa nad Bzurą |
E44335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bitwa kampanii wrześniowej |
C647
|
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: bitwa kampanii wrześniowej Context triple: [Bitwa nad Bzurą, instanceOf, bitwa kampanii wrześniowej]
-
A.
Soviet campaign
A Soviet campaign is a coordinated series of military, political, or propaganda operations conducted by the Soviet Union to achieve strategic objectives over a defined period and theater.
-
B.
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.
-
C.
battles
chosen
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.
-
D.
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.
-
E.
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.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:51 p.m.