Triple
T8173954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chernyakhovsky |
E190894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Slavic-language surname |
C17642
|
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: Slavic-language surname Context triple: [Chernyakhovsky, instanceOf, Slavic-language surname]
-
A.
South Slavic surname
A South Slavic surname is a family name originating from South Slavic-speaking regions, often reflecting ancestral occupations, personal traits, or geographic origins and typically following regional linguistic patterns and suffixes.
-
B.
Polish-language surname
A Polish-language surname is a family name originating from the Polish language, often reflecting ancestry, occupation, geography, or personal characteristics within Polish cultural and linguistic traditions.
-
C.
Slovak-language surname
A Slovak-language surname is a family name originating from or adapted to the Slovak language, typically reflecting Slovak phonology, morphology, and cultural naming traditions.
-
D.
Czech-language surname
A Czech-language surname is a family name originating from the Czech language, often reflecting Czech phonology, morphology, and cultural or geographic roots.
-
E.
Ukrainian-language surname
chosen
A Ukrainian-language surname is a family name originating from Ukrainian linguistic and cultural traditions, typically formed using characteristic Ukrainian phonetics, morphology, and suffixes.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:40 p.m.