Triple
T28951509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enfield poltergeist case |
E731027
|
entity |
| Predicate | involvedFamily |
P63314
|
FINISHED |
| Object | Hodgson family |
—
|
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: Hodgson family | Statement: [Enfield poltergeist case, involvedFamily, Hodgson family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedFamily Context triple: [Enfield poltergeist case, involvedFamily, Hodgson family]
-
A.
familyInvolvement
chosen
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
B.
interFamilyRelations
Indicates relationships or interactions that occur between different families or family units.
-
C.
familyAffectedBy
Indicates that one or more members of a person’s family experience or are impacted by a specified condition, event, or circumstance.
-
D.
leftFamily
Indicates that an entity has departed from or is no longer part of their family unit.
-
E.
familyAspect
Indicates a relationship where one entity is characterized by a particular familial role, status, or aspect in relation to another entity.
- 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_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 8:44 a.m.