Triple

T34664074
Position Surface form Disambiguated ID Type / Status
Subject Bashkirs E890201 entity
Predicate traditionalMusic P526 FINISHED
Object kurai flute
The kurai flute is a traditional Bashkir end-blown wind instrument known for its soft, melancholic tone and central role in the folk music and cultural heritage of the Bashkir people.
E2106669 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: kurai flute | Statement: [Bashkirs, traditionalMusic, kurai flute]
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: kurai flute
Triple: [Bashkirs, traditionalMusic, kurai flute]
Generated description
The kurai flute is a traditional Bashkir end-blown wind instrument known for its soft, melancholic tone and central role in the folk music and cultural heritage of the Bashkir 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_69f349d906bc8190b2efd9eff237d94b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f722f429e8819087d585e9976f0024 completed May 3, 2026, 10:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a374903aa648190b9beaf59b4562d53 completed June 21, 2026, 2:14 a.m.
NEDg Description generation batch_6a374a91d4f08190bc2df424a4136b3d completed June 21, 2026, 2:21 a.m.
NED2 Entity disambiguation (via description) batch_6a374b44cba88190999dede2bc2a408e completed June 21, 2026, 2:24 a.m.
Created at: May 1, 2026, 2:04 a.m.