Triple
T8411283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Mazepa |
E198629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian political figure |
C9036
|
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 political figure Context triple: [Ivan Mazepa, instanceOf, Ukrainian political figure]
-
A.
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.
-
B.
Ukrainian person
chosen
A Ukrainian person is an individual who identifies with the nation of Ukraine through citizenship, heritage, culture, or self-identification, often sharing Ukrainian language, traditions, and historical experiences.
-
C.
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.
-
D.
Czechoslovak politician
A Czechoslovak politician is a public figure who held governmental or party office in the former state of Czechoslovakia, influencing its domestic and foreign policies before its dissolution in 1993.
-
E.
Bulgarian politician
A Bulgarian politician is a public figure engaged in the governance and political life of Bulgaria, typically 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:05 p.m.