Triple
T29350091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izvestiya Tsentralnogo Ispolnitelnogo Komiteta |
E744282
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet newspaper |
C13140
|
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: Soviet newspaper Context triple: [Izvestiya Tsentralnogo Ispolnitelnogo Komiteta, instanceOf, Soviet newspaper]
-
A.
Russian newspaper
A Russian newspaper is a periodical publication, printed or digital, produced in the Russian language (or within Russia) that reports news, commentary, and other information relevant to Russian-speaking audiences.
-
B.
Soviet document
chosen
A Soviet document is an official or unofficial written record produced within the Soviet Union’s political, administrative, or social systems, reflecting its bureaucratic procedures, ideology, and historical context.
-
C.
Turkish newspaper
A Turkish newspaper is a periodical publication, printed or digital, produced in Turkey or in the Turkish language that reports news, commentary, and other information relevant to Turkish society and global events.
-
D.
Egyptian newspaper
An Egyptian newspaper is a periodical publication produced in Egypt that reports on national and international news, politics, culture, and public affairs, typically in Arabic and/or other languages, for a broad local and regional readership.
-
E.
Austrian newspaper
An Austrian newspaper is a periodical publication produced in Austria that reports on national and international news, politics, culture, and other topics relevant to Austrian readers.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:05 p.m.