Triple

T24112169
Position Surface form Disambiguated ID Type / Status
Subject Vohra E597405 entity
Predicate hasNotableBearer P458 FINISHED
Object Sanjay Vohra
Sanjay Vohra is an individual notable enough to be recognized as a bearer of the surname Vohra, though specific widely known public details about him are not clearly established.
E1719819 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: Sanjay Vohra | Statement: [Vohra, hasNotableBearer, Sanjay Vohra]
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: Sanjay Vohra
Triple: [Vohra, hasNotableBearer, Sanjay Vohra]
Generated description
Sanjay Vohra is an individual notable enough to be recognized as a bearer of the surname Vohra, though specific widely known public details about him are not clearly established.

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_69e288c60f9c8190af948d7354aedbeb completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1de1bd81c8190a44f07487d2ba176 completed April 29, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a119a1388dc81908d9f9001255a9868 completed May 23, 2026, 12:14 p.m.
NEDg Description generation batch_6a119aa510bc819083c4e8264616f63a completed May 23, 2026, 12:16 p.m.
NED2 Entity disambiguation (via description) batch_6a119b318d4881908d658464d8ea390c completed May 23, 2026, 12:18 p.m.
Created at: April 17, 2026, 11:03 p.m.