Triple
T31728123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleksandr Porfyrovych Arkhypenko |
E809783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ukrainian-American artist |
C58848
|
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-American artist Context triple: [Oleksandr Porfyrovych Arkhypenko, instanceOf, Ukrainian-American artist]
-
A.
Ukrainian-French artist
A Ukrainian-French artist is a creative professional of Ukrainian origin or heritage who lives in, is culturally connected to, or works significantly within France, producing art that often blends Ukrainian and French artistic traditions, histories, and perspectives.
-
B.
Polish-American artist
A Polish-American artist is a creator of visual, performing, or literary works whose identity and practice are shaped by both Polish cultural heritage and American social and artistic contexts.
-
C.
Russian-American artist
A Russian-American artist is a creative professional of Russian heritage who lives in or is closely connected to the United States, producing visual or other artistic works that often blend cultural influences from both Russian and American traditions.
-
D.
Polish-Russian artist
A Polish-Russian artist is a creative individual whose life, heritage, or practice is shaped by both Polish and Russian cultural, historical, and artistic influences.
-
E.
Soviet artist
A Soviet artist is a visual or performing creator who produced work within the Soviet Union’s political, social, and ideological framework, often navigating or embodying state-sanctioned styles such as Socialist Realism.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:20 p.m.