Triple
T26915839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Bakhtin |
E677514
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian literary theorist |
C24761
|
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: Russian literary theorist Context triple: [Mikhail Bakhtin, instanceOf, Russian literary theorist]
-
A.
Russian Formalist
chosen
A Russian Formalist is a literary theorist associated with the early 20th-century Russian movement that focused on the formal structures, devices, and functions of literary texts rather than their historical, biographical, or ideological contexts.
-
B.
Russian poet
A Russian poet is a literary artist from Russia who composes verse that reflects the country’s language, culture, history, and philosophical or emotional themes.
-
C.
Russian philosopher
A Russian philosopher is a thinker originating from or deeply engaged with the intellectual traditions of Russia, exploring fundamental questions about existence, knowledge, ethics, society, and culture within the context of Russian history, literature, and spiritual thought.
-
D.
Soviet scholar
A Soviet scholar is an academic or intellectual who conducted research, teaching, or theoretical work within the ideological, institutional, and political framework of the Soviet Union.
-
E.
Turkish literary scholar
A Turkish literary scholar is an academic who studies, analyzes, and interprets Turkish literature—its texts, authors, historical contexts, and critical theories—to deepen understanding of the Turkish literary tradition and its cultural significance.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:04 a.m.