Triple
T31112014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perron family |
E792973
|
entity |
| Predicate | timePeriodOfHaunting |
P165058
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Perron family, timePeriodOfHaunting, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfHaunting Context triple: [Perron family, timePeriodOfHaunting, 1970s]
-
A.
hasHauntingPeriod
chosen
Indicates a temporal relationship specifying the time span during which a haunting or ghostly presence is active or occurs.
-
B.
apparitionFrequency
Indicates how often an entity appears, manifests, or becomes perceptible within a given context or timeframe.
-
C.
haunts
Indicates that one entity persistently appears in, lingers around, or psychologically troubles another entity or place, often in a recurring or unsettling way.
-
D.
apparitionsDate
Indicates the date on which the apparitions are reported or believed to have occurred.
-
E.
hasHauntedLocation
Indicates that an entity possesses, is associated with, or includes a location that is believed to be haunted or supernaturally inhabited.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 9:04 p.m.