Triple
T8320132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Here’s Johnny!" |
E194808
|
entity |
| Predicate | usedInSubgenre |
P71102
|
FINISHED |
| Object | psychological horror |
—
|
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: psychological horror | Statement: ["Here’s Johnny!", usedInSubgenre, psychological horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSubgenre Context triple: ["Here’s Johnny!", usedInSubgenre, psychological horror]
-
A.
subgenre
Indicates that one genre is a more specific, subordinate category within a broader parent genre.
-
B.
secondaryGenre
chosen
Indicates that an entity (such as a work or item) has an additional, non-primary genre classification associated with it.
-
C.
coveredInGenre
Indicates that a work or item is associated with, categorized under, or treated within a particular genre.
-
D.
alsoUsedIn
Indicates that something is additionally employed, applied, or present in another context, setting, or use case beyond the primary one.
-
E.
hasUseGenre
Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f6686a0819094abc2bfd2e500a5 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.