Triple
T28951511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enfield poltergeist case |
E731027
|
entity |
| Predicate | reportedPhenomena |
P84275
|
FINISHED |
| Object | poltergeist activity |
—
|
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: poltergeist activity | Statement: [Enfield poltergeist case, reportedPhenomena, poltergeist activity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedPhenomena Context triple: [Enfield poltergeist case, reportedPhenomena, poltergeist activity]
-
A.
encounteredPhenomenon
Indicates that an entity has come across, experienced, or observed a particular phenomenon.
-
B.
allegedPhenomenon
chosen
Indicates that something is claimed or reported to be a phenomenon, but its existence, cause, or nature is uncertain or disputed.
-
C.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
D.
possibleSightings
Indicates that there are reported or potential observations of one entity by another or at a particular place or time.
-
E.
examplePhenomenon
Indicates a representative or illustrative occurrence used to demonstrate or clarify a broader phenomenon or pattern.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 8:44 a.m.