Triple

T32598873
Position Surface form Disambiguated ID Type / Status
Subject Manti E833307 entity
Predicate hasVariant P455 FINISHED
Object Kayseri mantisi
Kayseri mantısı is a traditional Turkish dumpling specialty from the city of Kayseri, known for its tiny, meat-filled parcels typically served with yogurt and a spiced butter sauce.
E2014732 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: Kayseri mantisi | Statement: [Manti, hasVariant, Kayseri mantisi]
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: Kayseri mantisi
Triple: [Manti, hasVariant, Kayseri mantisi]
Generated description
Kayseri mantısı is a traditional Turkish dumpling specialty from the city of Kayseri, known for its tiny, meat-filled parcels typically served with yogurt and a spiced butter sauce.

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_69f3492ab63c8190aec24d5003b47c29 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c698588c819088e3bc33318651f3 completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a348610c814819099d10d4cfbf2165f completed June 18, 2026, 11:58 p.m.
NEDg Description generation batch_6a3486d538a0819085111e56e3d52e43 completed June 19, 2026, 12:01 a.m.
NED2 Entity disambiguation (via description) batch_6a34886f9d5c8190852be44ccf6ea9fa completed June 19, 2026, 12:08 a.m.
Created at: May 1, 2026, 1:05 a.m.