Triple
T11358042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milorg |
E269012
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Norwegian resistance organization |
C30043
|
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: Norwegian resistance organization Context triple: [Milorg, instanceOf, Norwegian 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.
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.
-
D.
Kurdish nationalist organization
A Kurdish nationalist organization is a group dedicated to promoting Kurdish self-determination, cultural identity, and political rights, often advocating for autonomy or independence for Kurdish-populated regions.
-
E.
Kurdish organization
A Kurdish organization is a structured group formed by Kurdish individuals or allies to advance Kurdish political, cultural, social, or humanitarian interests at local, national, or international levels.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.