Triple
T1118916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Polish Army |
E11164
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish Armed Forces in the East formation |
C2904
|
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: Polish Armed Forces in the East formation Context triple: [2nd Polish Army, instanceOf, Polish Armed Forces in the East formation]
-
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.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
German prisoner-of-war camp system
The German prisoner-of-war camp system was a network of military-run facilities in Nazi Germany and occupied territories designed to detain, control, and exploit captured enemy combatants under varying conditions that often violated international law.
-
D.
World War II military formation
chosen
A World War II military formation is an organized grouping of military units—such as divisions, corps, or armies—structured and deployed by a nation’s armed forces during the Second World War to conduct coordinated combat and support operations.
-
E.
German soldiers
German soldiers are military personnel serving in Germany’s armed forces, historically or presently, who are trained, organized, and equipped to conduct defense and combat operations under German command.
- 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.