Triple
T21528577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Haunting of Black Wood |
E531166
|
entity |
| Predicate | usesHorrorType |
P117175
|
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: [The Haunting of Black Wood, usesHorrorType, psychological horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHorrorType Context triple: [The Haunting of Black Wood, usesHorrorType, psychological horror]
-
A.
hasHorrorElements
Indicates that something contains features, themes, or stylistic aspects characteristic of the horror genre.
-
B.
hasHorrorSubgenre
chosen
Indicates that a horror work is classified as belonging to a specific horror subgenre.
-
C.
notableFear
Indicates that one entity is especially afraid of, or has a significant fear related to, another entity.
-
D.
hasTypeOfUseInFilm
Indicates that something is associated with a specific manner or category of use within the context of a film.
-
E.
containsSupernaturalElement
Indicates that the subject involves or features a supernatural, magical, or otherworldly element beyond normal natural laws.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8852e68c8190a5341c9f75081382 |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.