Triple
T5901714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georg Elser |
E131241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German resistance fighter |
C4781
|
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: German resistance fighter Context triple: [Georg Elser, instanceOf, German resistance fighter]
-
A.
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.
-
B.
resistance fighter
chosen
A resistance fighter is an individual who actively opposes and combats an occupying force, oppressive regime, or unjust authority, often through clandestine, guerrilla, or subversive means.
-
C.
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.
-
D.
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.
-
E.
Jewish resistance organization
A Jewish resistance organization is a clandestine or organized group formed by Jews to oppose, sabotage, or survive oppressive regimes, antisemitic persecution, or genocidal policies through political, military, cultural, or humanitarian means.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.