Triple
T9963006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klaus Bonhoeffer |
E195613
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the German Resistance |
C3437
|
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: member of the German Resistance Context triple: [Klaus Bonhoeffer, instanceOf, member of the German Resistance]
-
A.
World War II resistance member
chosen
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.
member of the Bonhoeffer family
A member of the Bonhoeffer family is an individual belonging by birth or legal relation to the historically significant German Bonhoeffer lineage, known for its intellectual, theological, and resistance contributions.
-
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.
resistance fighter
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.
-
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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:47 p.m.