Triple

T36849900
Position Surface form Disambiguated ID Type / Status
Subject Rumbur dialect E910646 entity
Predicate closelyRelatedTo P37 FINISHED
Object Bumburet dialect
The Bumburet dialect is a variety of the Kalasha language spoken in Pakistan’s Bumburet Valley, closely associated with the culture and traditions of the Kalash people.
E2201071 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: Bumburet dialect | Statement: [Rumbur dialect, closelyRelatedTo, Bumburet dialect]
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: Bumburet dialect
Triple: [Rumbur dialect, closelyRelatedTo, Bumburet dialect]
Generated description
The Bumburet dialect is a variety of the Kalasha language spoken in Pakistan’s Bumburet Valley, closely associated with the culture and traditions of the Kalash people.

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_69f76e8033d48190a59274f86f13be48 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7cfab991c8190a6672a33d43b6652 completed May 3, 2026, 10:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3dde7a4e90819097a54197a6bb4a3d completed June 26, 2026, 2:05 a.m.
NEDg Description generation batch_6a3de387035881908df747ec23d9e3cb completed June 26, 2026, 2:27 a.m.
NED2 Entity disambiguation (via description) batch_6a3dee75875881908c3f34cbd60945a9 completed June 26, 2026, 3:13 a.m.
Created at: May 3, 2026, 4:13 p.m.