Triple
T17130656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemming Juncker |
E415712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Danish resistance member |
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: Danish resistance member Context triple: [Flemming Juncker, instanceOf, Danish resistance member]
-
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.
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.
-
C.
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.
-
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.
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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:36 a.m.