Triple

T36324533
Position Surface form Disambiguated ID Type / Status
Subject Deadly Blessing E894424 entity
Predicate screenwriter P2831 FINISHED
Object Glenn M. Benest
Glenn M. Benest is an American screenwriter and producer known for his work in horror and thriller films, as well as for teaching and mentoring aspiring screenwriters.
E2295170 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: Glenn M. Benest | Statement: [Deadly Blessing, screenwriter, Glenn M. Benest]
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: Glenn M. Benest
Triple: [Deadly Blessing, screenwriter, Glenn M. Benest]
Generated description
Glenn M. Benest is an American screenwriter and producer known for his work in horror and thriller films, as well as for teaching and mentoring aspiring screenwriters.

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_69f76e4dcf088190a6c3216c209cab52 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba4930d0819094def368fd8a73b0 completed May 3, 2026, 9:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7d13453be08190b404f2df5a36d79b completed Aug. 13, 2026, 12:43 a.m.
NEDg Description generation batch_6a7d139b0b0881908f19f82d03e68951 completed Aug. 13, 2026, 12:45 a.m.
NED2 Entity disambiguation (via description) batch_6a7d14039d0c819087cc6ed43216cfc2 completed Aug. 13, 2026, 12:46 a.m.
Created at: May 3, 2026, 4:09 p.m.