Triple
T30318949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Amityville Horror (2005 film) |
E771133
|
entity |
| Predicate | houseDepictedAs |
P15073
|
FINISHED |
| Object | supposedly haunted house |
—
|
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: supposedly haunted house | Statement: [The Amityville Horror (2005 film), houseDepictedAs, supposedly haunted house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseDepictedAs Context triple: [The Amityville Horror (2005 film), houseDepictedAs, supposedly haunted house]
-
A.
house1
Indicates that something is identified or classified as a house or dwelling.
-
B.
house2
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
-
C.
depictsResidence
chosen
Indicates that one entity visually represents or portrays the place where another entity lives or resides.
-
D.
houseElement
Indicates that one entity is a structural or functional component of a house associated with another entity.
-
E.
houseSeat
Indicates that a particular location or structure serves as the primary residence or official dwelling place for an 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 7:51 p.m.