Triple
T24293837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongoose, R.I.P. |
E605898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Cold War espionage novel |
C19297
|
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 espionage novel Context triple: [Mongoose, R.I.P., instanceOf, Cold War espionage novel]
-
A.
Cold War novel
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
chosen
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.
espionage film
An espionage film is a movie genre that centers on spies, covert operations, and international intrigue, often involving political or military secrets, deception, and high-stakes missions.
-
D.
espionage franchise
An espionage franchise is a recurring series of related stories, often spanning films, books, games, or TV, that centers on spies, covert operations, and intelligence agencies navigating high-stakes political or criminal intrigue.
-
E.
Cold War operation
A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.