Triple

T28639880
Position Surface form Disambiguated ID Type / Status
Subject Paranoid E724890 entity
Predicate hasMainCharacter P1183 FINISHED
Object Nina Suresh
Nina Suresh is one of the central protagonists in the British psychological crime drama series "Paranoid," portrayed as a determined yet emotionally vulnerable detective.
E1853256 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: Nina Suresh | Statement: [Paranoid, hasMainCharacter, Nina Suresh]
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: Nina Suresh
Triple: [Paranoid, hasMainCharacter, Nina Suresh]
Generated description
Nina Suresh is one of the central protagonists in the British psychological crime drama series "Paranoid," portrayed as a determined yet emotionally vulnerable detective.

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_69f01d8328c48190bc0e5f9b9b848582 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f652a9d4608190b55bd721a3de7cac completed May 2, 2026, 7:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2550359e7c819093435f839974c06d completed June 7, 2026, 11:04 a.m.
NEDg Description generation batch_6a25547c1cb881909b0a85b2bb6d61f1 completed June 7, 2026, 11:22 a.m.
NED2 Entity disambiguation (via description) batch_6a2558d26f808190b01d391c806b780d completed June 7, 2026, 11:41 a.m.
Created at: April 28, 2026, 4:43 a.m.