Triple

T25709759
Position Surface form Disambiguated ID Type / Status
Subject Someone’s Knocking at the Door E644696 entity
Predicate hasCinematographyBy P1953 FINISHED
Object Christian Janss
Christian Janss is a cinematographer best known for his work on the psychological horror film "Someone’s Knocking at the Door."
E1736629 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: Christian Janss | Statement: [Someone’s Knocking at the Door, hasCinematographyBy, Christian Janss]
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: Christian Janss
Triple: [Someone’s Knocking at the Door, hasCinematographyBy, Christian Janss]
Generated description
Christian Janss is a cinematographer best known for his work on the psychological horror film "Someone’s Knocking at the Door."

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_69e77e83c8ec8190bf52fcdac4838984 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5fc14ae5c8190acfecf5bb5d3c5d6 completed May 2, 2026, 1:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11fe429e888190b9b3f75242879c47 completed May 23, 2026, 7:21 p.m.
NEDg Description generation batch_6a11fed8fd9881908e6822bc418066e6 completed May 23, 2026, 7:24 p.m.
NED2 Entity disambiguation (via description) batch_6a11ff33e3448190996da2faf6f3f6b5 completed May 23, 2026, 7:25 p.m.
Created at: April 21, 2026, 9:10 p.m.