Triple
T12594838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarusian literature |
E300706
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | East Slavic literature |
C32193
|
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: East Slavic literature Context triple: [Belarusian literature, instanceOf, East Slavic literature]
-
A.
Slavic culture
Slavic culture encompasses the shared languages, traditions, folklore, religious practices, and social customs of the diverse Slavic peoples of Eastern, Central, and Southeastern Europe.
-
B.
West Slavic languages
West Slavic languages are a subgroup of the Slavic language family, including Polish, Czech, Slovak, and related languages, primarily spoken in Central Europe and characterized by shared phonological, grammatical, and lexical features.
-
C.
North Germanic literature
North Germanic literature encompasses the written and oral literary traditions produced in the North Germanic languages (such as Old Norse, Icelandic, Norwegian, Danish, and Swedish), from medieval sagas and eddas to modern prose and poetry.
-
D.
Turkic literature
Turkic literature encompasses the oral and written literary traditions produced in Turkic languages across Central Asia, Anatolia, the Caucasus, and surrounding regions, reflecting diverse historical, cultural, and religious influences.
-
E.
East Slavic polity
An East Slavic polity is a historically or contemporarily organized political entity—such as a state, principality, or federation—primarily inhabited and shaped by East Slavic peoples and their cultural, linguistic, and religious traditions.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:08 p.m.