Triple
T35606053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autopsy Room Four (short story) |
E1028893
|
entity |
| Predicate | usesHorrorTrope |
P68123
|
FINISHED |
| Object | premature autopsy |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: premature autopsy | Statement: [Autopsy Room Four (short story), usesHorrorTrope, premature autopsy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHorrorTrope Context triple: [Autopsy Room Four (short story), usesHorrorTrope, premature autopsy]
-
A.
usedAsTrope
chosen
Indicates that something functions as a recurring narrative device, motif, or cliché within a story or set of stories.
-
B.
subvertsTrope
Indicates that one entity challenges, undermines, or reverses the expected pattern or convention represented by a particular trope.
-
C.
usesHorrorAsMetaphorFor
Indicates that something employs horror elements or themes as a symbolic device to represent, comment on, or explore another concept, issue, or experience.
-
D.
inspiredTrope
Indicates that one trope serves as the creative or conceptual inspiration for another trope.
-
E.
hasHorrorElements
Indicates that something contains features, themes, or stylistic aspects characteristic of the horror genre.
- F. None of above.
Provenance (3 batches)
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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec6408081908e8a1eee79363cb0 |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.