Triple
T2791061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henryk Sucharski |
E61928
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II prisoner of war |
C866
|
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: World War II prisoner of war Context triple: [Henryk Sucharski, instanceOf, World War II prisoner of war]
-
A.
WorldWarIIPOWs
chosen
WorldWarIIPOWs represents individuals captured and detained as prisoners of war during World War II, encompassing their status, treatment, affiliations, and experiences under international and wartime conditions.
-
B.
prisonersOfWar
prisonersOfWar are individuals captured by an enemy during an armed conflict and held under specific legal protections and obligations defined by international humanitarian law.
-
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 veteran
A World War II veteran is an individual who served in the armed forces of any nation during the global conflict of 1939–1945, participating in military operations or support roles related to the war.
-
E.
World War II resistance member
A World War II resistance member is an individual who clandestinely opposed Axis occupation or authoritarian regimes through activities such as sabotage, intelligence gathering, underground communication, and support for persecuted populations.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:58 p.m.