Triple

T22951753
Position Surface form Disambiguated ID Type / Status
Subject Anuradha Paudwal E570037 entity
Predicate hasSpouse P13 FINISHED
Object Arun Paudwal
Arun Paudwal was an Indian music composer and arranger known for his work in Bollywood films and devotional music, and for being married to playback singer Anuradha Paudwal.
E1683542 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: Arun Paudwal | Statement: [Anuradha Paudwal, hasSpouse, Arun Paudwal]
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: Arun Paudwal
Triple: [Anuradha Paudwal, hasSpouse, Arun Paudwal]
Generated description
Arun Paudwal was an Indian music composer and arranger known for his work in Bollywood films and devotional music, and for being married to playback singer Anuradha Paudwal.

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_69e2459199d08190a8184ee2aa935842 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f181a285448190a718734fe933d51a completed April 29, 2026, 3:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad1b164c81909e374fa0b402f137 completed May 22, 2026, 7:23 p.m.
NEDg Description generation batch_6a10aeae38748190a970045e9bbd49f7 completed May 22, 2026, 7:29 p.m.
NED2 Entity disambiguation (via description) batch_6a10af5c912c81908164148277047f40 completed May 22, 2026, 7:32 p.m.
Created at: April 17, 2026, 3:46 p.m.