Triple
T22345830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partisans Armés |
E552388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belgian Resistance organization |
C46141
|
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 organization Context triple: [Partisans Armés, instanceOf, Belgian Resistance organization]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Dutch rebel group
A Dutch rebel group is an organized, often clandestine collective in the Netherlands that uses resistance, protest, or insurgent tactics to oppose established political, social, or economic authorities.
-
E.
Norwegian resistance organization
A Norwegian resistance organization is a clandestine group formed to oppose and undermine occupying or oppressive forces in Norway through activities such as intelligence gathering, sabotage, and support for the civilian population.
- F. None of above. chosen
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.