Triple
T16524678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Code to Zero |
E401403
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cold War fiction |
C9255
|
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: Cold War fiction Context triple: [Code to Zero, instanceOf, Cold War fiction]
-
A.
Cold War novel
chosen
A Cold War novel is a work of fiction set during or shaped by the geopolitical tensions between the Western and Eastern blocs, typically exploring themes of espionage, ideological conflict, nuclear anxiety, and the personal impact of global rivalry.
-
B.
espionage literature
Espionage literature is a genre of fiction and nonfiction that centers on spies, covert operations, and intelligence agencies, exploring themes of secrecy, betrayal, political intrigue, and moral ambiguity.
-
C.
Cold War era case
A Cold War era case is a legal or historical instance arising between roughly 1947 and 1991 that reflects or is shaped by the geopolitical tensions, ideological conflicts, and security concerns between the United States and the Soviet Union and their respective allies.
-
D.
World War II novel
A World War II novel is a work of fiction set during the Second World War that explores the experiences, struggles, and moral complexities of individuals or societies affected by the global conflict.
-
E.
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.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:14 a.m.