Triple
T22346111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Guérisse |
E552395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belgian resistance member |
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: Belgian resistance member Context triple: [Albert Guérisse, instanceOf, Belgian resistance member]
-
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.
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.
-
C.
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.
-
D.
World War II resistance group
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.
-
E.
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.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.