Triple

T33010963
Position Surface form Disambiguated ID Type / Status
Subject Southern Kosovo E844642 entity
Predicate contains P35 FINISHED
Object Mamusha municipality
Mamusha municipality is a small, predominantly rural local government area in southern Kosovo known for its agricultural production and Turkish-speaking community.
E2032833 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: Mamusha municipality | Statement: [Southern Kosovo, contains, Mamusha municipality]
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: Mamusha municipality
Triple: [Southern Kosovo, contains, Mamusha municipality]
Generated description
Mamusha municipality is a small, predominantly rural local government area in southern Kosovo known for its agricultural production and Turkish-speaking community.

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_69f3494f3b4081909dccf2af34372a26 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d27eeb708190a7d9848430a3e43c completed May 3, 2026, 4:43 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34dad31c608190bf079c21b0f462a9 completed June 19, 2026, 5:59 a.m.
NEDg Description generation batch_6a34dc87c52081908c2b9d16c346976b completed June 19, 2026, 6:07 a.m.
NED2 Entity disambiguation (via description) batch_6a34dd1aa0f08190b5dad7af7e9220c0 completed June 19, 2026, 6:09 a.m.
Created at: May 1, 2026, 1:23 a.m.