Triple

T29443947
Position Surface form Disambiguated ID Type / Status
Subject The Curse E746793 entity
Predicate partOfSeries P1761 FINISHED
Object The Curse film series
The Curse film series is a collection of low-budget 1980s horror movies loosely connected by themes of supernatural or science-fiction curses rather than by a continuous storyline.
E1865676 NE 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: The Curse film series | Statement: [The Curse, partOfSeries, The Curse film series]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: The Curse film series
Triple: [The Curse, partOfSeries, The Curse film series]
Generated description
The Curse film series is a collection of low-budget 1980s horror movies loosely connected by themes of supernatural or science-fiction curses rather than by a continuous storyline.

Provenance (5 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_69f0a7a180e48190ae775e40047dbcb5 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f66b1f46cc8190aeed9e77976f5cd1 completed May 2, 2026, 9:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25d939753481908ddf552e0838cd40 completed June 7, 2026, 8:48 p.m.
NEDg Description generation batch_6a25dd5104608190877dea3df07243ac completed June 7, 2026, 9:06 p.m.
NED2 Entity disambiguation (via description) batch_6a25ddb248c08190902a450290a618f1 completed June 7, 2026, 9:08 p.m.
Created at: April 28, 2026, 3:25 p.m.