Triple
T20999345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Amityville Horror |
E517241
|
entity |
| Predicate | influentialWorkIn |
P1994
|
FINISHED |
| Object | horror cinema |
—
|
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: horror cinema | Statement: [The Amityville Horror, influentialWorkIn, horror cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influentialWorkIn Context triple: [The Amityville Horror, influentialWorkIn, horror cinema]
-
A.
influencedWork
chosen
Indicates that one work has had a significant impact on the creation, style, content, or development of another work.
-
B.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
C.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
D.
majorWorkAboutHim
Indicates that a major work (such as a book, film, or study) is primarily about the referenced person.
-
E.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc2395108190871e173354e4ef6f |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:51 p.m.