Triple
T22618762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiße Rose |
E558216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Widerstandsgruppe |
C30044
|
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: Widerstandsgruppe Context triple: [Weiße Rose, instanceOf, Widerstandsgruppe]
-
A.
Polish resistance organization
A Polish resistance organization is a clandestine group formed in Poland to oppose and undermine occupying or oppressive regimes through coordinated political, military, and intelligence activities.
-
B.
Greek resistance organization
A Greek resistance organization is a clandestine group formed within Greece to oppose and undermine occupying or authoritarian regimes through coordinated political, military, and intelligence activities.
-
C.
World War II resistance group
chosen
A World War II resistance group is an organized, often clandestine network of civilians and fighters who opposed and actively undermined Axis occupation or control through sabotage, intelligence gathering, and support for Allied forces.
-
D.
Czechoslovak exile unit
A Czechoslovak exile unit is a military formation composed of Czechoslovak personnel organized outside their occupied homeland, typically under foreign command, to continue armed resistance or fulfill allied military roles.
-
E.
Dutch resistance organization
A Dutch resistance organization is a clandestine group formed in the Netherlands to oppose and undermine occupying or oppressive regimes through activities such as sabotage, intelligence gathering, and aiding persecuted individuals.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3 p.m.