Triple
T5807097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergei Khrushchev |
E128772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historian of the Cold War |
C5584
|
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: historian of the Cold War Context triple: [Sergei Khrushchev, instanceOf, historian of the Cold War]
-
A.
Cold War history topic
A Cold War history topic is a focused subject area examining the political, military, economic, ideological, or cultural dimensions of the global rivalry between the United States and the Soviet Union from roughly 1945 to 1991.
-
B.
Cold War political elite
A Cold War political elite is a small, influential group of government and party leaders who shaped and directed national and international policies within the ideological, military, and diplomatic tensions between the Western and Eastern blocs from roughly 1945 to 1991.
-
C.
American historian
An American historian is a scholar who researches, analyzes, and interprets the history of the United States, its people, institutions, and interactions with the wider world.
-
D.
Cold War polity
A Cold War polity is a state or political entity whose institutions, policies, and international behavior are fundamentally shaped by the ideological, military, and geopolitical tensions between the U.S.-led Western bloc and the Soviet-led Eastern bloc from roughly 1947 to 1991.
-
E.
Soviet scholar
chosen
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.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.