Triple
T18589496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutz family |
E454324
|
entity |
| Predicate | allegedlyExperienced |
P132701
|
FINISHED |
| Object | terrifying paranormal events |
—
|
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: terrifying paranormal events | Statement: [Lutz family, allegedlyExperienced, terrifying paranormal events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedlyExperienced Context triple: [Lutz family, allegedlyExperienced, terrifying paranormal events]
-
A.
hasGlobalExperience
Indicates that an entity possesses experience gained from working, operating, or engaging across multiple countries or international contexts.
-
B.
typeOfExperience
Indicates that one entity specifies the category or nature of an experience associated with another entity.
-
C.
basedOnExperience
Indicates that something is determined, chosen, or formed according to prior experience or experiential knowledge.
-
D.
hasExperienceElement
Indicates that an experience is composed of, or includes, a specific constituent element or component.
-
E.
providesExperienceOf
Indicates that one entity enables or delivers the experience of another entity to someone or something.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b4a2a0819098047ee81278bd9d |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:44 a.m.