Triple
T33254874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Man Who Killed Kennedy: The Case Against LBJ |
E851348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conspiracy literature |
C32187
|
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: conspiracy literature Context triple: [The Man Who Killed Kennedy: The Case Against LBJ, instanceOf, conspiracy literature]
-
A.
conspiracy fiction
Conspiracy fiction is a narrative genre that centers on secret plots by powerful, often hidden organizations or forces, exploring themes of paranoia, mistrust, and the uncovering of concealed truths.
-
B.
political conspiracy
A political conspiracy is a covert agreement or coordinated effort by a group to manipulate, undermine, or unlawfully influence political power, processes, or outcomes for their own advantage.
-
C.
conspiracy theory topic
chosen
A conspiracy theory topic is a subject or event around which people construct and share unverified, often elaborate explanations that attribute hidden, coordinated actions or intentions to powerful individuals or groups.
-
D.
conspiracy theorist
A conspiracy theorist is a person who persistently interprets events as the result of secret, powerful, and often malevolent plots, typically rejecting official or mainstream explanations.
-
E.
pseudoarchaeology literature
Pseudoarchaeology literature consists of books and writings that present speculative, unscientific, or debunked interpretations of archaeological evidence, often emphasizing sensational claims about ancient civilizations, lost technologies, or extraterrestrial influences.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.