Triple
T12994923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordedienst |
E322008
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch resistance organization |
C32307
|
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: Dutch resistance organization Context triple: [Ordedienst, instanceOf, Dutch resistance organization]
-
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.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:44 p.m.