Triple
T31112010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perron family |
E792973
|
entity |
| Predicate | allegedParanormalActivity |
P84275
|
FINISHED |
| Object | apparitions |
—
|
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: apparitions | Statement: [Perron family, allegedParanormalActivity, apparitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedParanormalActivity Context triple: [Perron family, allegedParanormalActivity, apparitions]
-
A.
allegedPhenomenon
chosen
Indicates that something is claimed or reported to be a phenomenon, but its existence, cause, or nature is uncertain or disputed.
-
B.
apparitionWitnessCount
Indicates the number of distinct observers who witnessed a particular apparition event.
-
C.
apparitionsWitnessedBy
Indicates that one entity is an apparition or ghostly phenomenon that has been seen or experienced by another entity.
-
D.
causeOfSupernaturalEvents
Indicates a relationship where an entity is the source or origin of supernatural events affecting another entity or situation.
-
E.
apparitionWitnessType
Indicates the specific manner or role in which an apparition is witnessed or experienced by an observer.
- 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_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 9:04 p.m.