Triple

T23576763
Position Surface form Disambiguated ID Type / Status
Subject Khandeshi language E580276 entity
Predicate hasAlternativeName P39 FINISHED
Object Ahirani-Khandeshi
Ahirani-Khandeshi is an Indo-Aryan language variety spoken primarily in the Khandesh region of Maharashtra, India, closely related to Marathi and other neighboring dialects.
E1597514 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: Ahirani-Khandeshi | Statement: [Khandeshi language, hasAlternativeName, Ahirani-Khandeshi]
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: Ahirani-Khandeshi
Triple: [Khandeshi language, hasAlternativeName, Ahirani-Khandeshi]
Generated description
Ahirani-Khandeshi is an Indo-Aryan language variety spoken primarily in the Khandesh region of Maharashtra, India, closely related to Marathi and other neighboring dialects.

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_69e24601a9108190bc31e83833c980e4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1afd6608481909a0d293ba8f65b2b completed April 29, 2026, 7:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f4570919c8190a0cde4de9941eb48 completed May 21, 2026, 5:48 p.m.
NEDg Description generation batch_6a0f4993b2b4819096eadd033cda306d completed May 21, 2026, 6:06 p.m.
NED2 Entity disambiguation (via description) batch_6a0f4a54f09c81909762ebf10c69b0f6 completed May 21, 2026, 6:09 p.m.
Created at: April 17, 2026, 6:38 p.m.