Triple
T9261400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukrainian Insurgent Army |
E222587
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian nationalist organization |
C25878
|
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: Ukrainian nationalist organization Context triple: [Ukrainian Insurgent Army, instanceOf, Ukrainian nationalist organization]
-
A.
Greek nationalist organization
A Greek nationalist organization is a group that promotes the political, cultural, and territorial interests of the Greek nation, often emphasizing national identity, sovereignty, and historical continuity.
-
B.
Rusyn organization
A Rusyn organization is a formal group or institution dedicated to representing, preserving, and promoting the cultural, social, political, or educational interests of the Rusyn people.
-
C.
Afrikaner nationalist organization
An Afrikaner nationalist organization is a group dedicated to promoting and preserving the political, cultural, and economic interests, identity, and self-determination of Afrikaners, often emphasizing Afrikaans language, heritage, and nationalist ideology.
-
D.
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.
-
E.
Crimean Tatar organization
A Crimean Tatar organization is a formal group or institution established by or for Crimean Tatars to represent their interests, preserve their culture and language, and address social, political, or community issues.
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:32 p.m.