Triple

T32172227
Position Surface form Disambiguated ID Type / Status
Subject Escape Plan E821738 entity
Predicate mainCharacter P1183 FINISHED
Object Emil Rottmayer
Emil Rottmayer is a central character in the action thriller film "Escape Plan," portrayed as a mysterious inmate who partners with the protagonist to engineer a high-stakes prison break.
E2296299 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: Emil Rottmayer | Statement: [Escape Plan, mainCharacter, Emil Rottmayer]
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: Emil Rottmayer
Triple: [Escape Plan, mainCharacter, Emil Rottmayer]
Generated description
Emil Rottmayer is a central character in the action thriller film "Escape Plan," portrayed as a mysterious inmate who partners with the protagonist to engineer a high-stakes prison break.

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_69f3490699a48190bbef96b198e8fade completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6ba75e89481908163f7c227094a4e completed May 3, 2026, 3:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a825bd674088190bedfe3fd6bede5cc completed Aug. 17, 2026, 12:54 a.m.
NEDg Description generation batch_6a825e1845dc8190a50f23f893e10f14 completed Aug. 17, 2026, 1:04 a.m.
NED2 Entity disambiguation (via description) batch_6a825e6afb188190ba77438b509b555f completed Aug. 17, 2026, 1:05 a.m.
Created at: May 1, 2026, 12:33 a.m.