Triple
T29357559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stepan Bandera |
E744487
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian nationalist politician |
C24081
|
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 politician Context triple: [Stepan Bandera, instanceOf, Ukrainian nationalist politician]
-
A.
Ukrainian independence activist
chosen
A Ukrainian independence activist is an individual who actively advocates, organizes, and mobilizes support for Ukraine’s political sovereignty, territorial integrity, and self-determination against foreign domination or influence.
-
B.
Slovak nationalist politician
A Slovak nationalist politician is a political figure who advocates for the promotion, protection, and prioritization of Slovak national identity, sovereignty, culture, and interests within domestic and international politics.
-
C.
Nevisian politician
A Nevisian politician is a public official from the island of Nevis who participates in governing, policymaking, and political representation at the local, national, or regional level.
-
D.
Belarusian politician
A Belarusian politician is an individual actively involved in the governance, political decision-making, or public administration of Belarus, typically holding or seeking a public office within its political system.
-
E.
Hungarian politician
A Hungarian politician is a public figure who participates in the governance and political decision-making processes of Hungary, typically by holding or seeking elected or appointed office at the local, regional, or national level.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:14 p.m.