Triple
T29488843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petro Kosach |
E748011
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian public 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 public figure Context triple: [Petro Kosach, instanceOf, Ukrainian public figure]
-
A.
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.
-
B.
Russian public figure
A Russian public figure is an individual who holds a prominent, recognizable role in Russian society—such as in politics, media, culture, or business—and whose actions and opinions attract significant public and media attention.
-
C.
Ukrainian independence activist
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.
-
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.
member of the Ukrainian intelligentsia
A member of the Ukrainian intelligentsia is an educated cultural, academic, or professional figure who actively shapes and reflects Ukrainian national identity, thought, and public life through intellectual, artistic, or civic engagement.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:11 p.m.