Triple
T29994671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Liberation Army |
E761986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborationist military formation |
C50611
|
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: collaborationist military formation Context triple: [Russian Liberation Army, instanceOf, collaborationist military formation]
-
A.
collaborationist organization
chosen
A collaborationist organization is a group that cooperates with an occupying or dominant foreign power, often against the interests or resistance of its own society or nation.
-
B.
collaborationist government
A collaborationist government is a regime established or maintained in cooperation with an occupying or foreign power, often administering local affairs while supporting the occupier’s political, military, or economic objectives.
-
C.
collaborationist movement
A collaborationist movement is a political or social group within an occupied or dominated society that actively cooperates with an external power, often in pursuit of perceived benefits, survival, or ideological alignment.
-
D.
rebel group military formation
A rebel group military formation is an organized, non-state armed unit structured to conduct coordinated combat or insurgent operations against established authorities or rival forces.
-
E.
Jewish auxiliary police force
A Jewish auxiliary police force is a locally recruited, often collaborationist law enforcement unit composed of Jewish personnel operating under occupying or external authorities, typically during periods of conflict or foreign control.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:39 p.m.