Triple
T32121921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluckley |
E820398
|
entity |
| Predicate | hasHauntedLocation |
P176361
|
FINISHED |
| Object | The Screaming Woods |
—
|
NE NERFINISHED |
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: The Screaming Woods | Statement: [Pluckley, hasHauntedLocation, The Screaming Woods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHauntedLocation Context triple: [Pluckley, hasHauntedLocation, The Screaming Woods]
-
A.
isHauntedLocation
Indicates that a location is supernaturally affected or inhabited by ghosts, spirits, or other paranormal entities.
-
B.
hasHauntingPeriod
Indicates a temporal relationship specifying the time span during which a haunting or ghostly presence is active or occurs.
-
C.
hasCursedLocation
Indicates a relationship where a location is affected by or associated with a curse.
-
D.
haunts
Indicates that one entity persistently appears in, lingers around, or psychologically troubles another entity or place, often in a recurring or unsettling way.
-
E.
hasGhostHouse
Indicates that an entity possesses, contains, or is associated with a house believed to be haunted or inhabited by ghosts.
- F. None of above. chosen
Provenance (4 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 12:28 a.m.