Triple

T30866804
Position Surface form Disambiguated ID Type / Status
Subject Yambol Province E786224 entity
Predicate hasMunicipality P847 FINISHED
Object Tundzha Municipality
Tundzha Municipality is an administrative region in southeastern Bulgaria known for its predominantly rural character and location within Yambol Province.
E1938748 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: Tundzha Municipality | Statement: [Yambol Province, hasMunicipality, Tundzha 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: Tundzha Municipality
Triple: [Yambol Province, hasMunicipality, Tundzha Municipality]
Generated description
Tundzha Municipality is an administrative region in southeastern Bulgaria known for its predominantly rural character and location within Yambol Province.

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_69f224b9df2c819086f55f8bcf7f382e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f691acf6d481909e6763574daee4cb completed May 3, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a28e45664e88190beea7cf561b07f65 completed June 10, 2026, 4:13 a.m.
NEDg Description generation batch_6a28e58730e08190ad82721597fd7fd9 completed June 10, 2026, 4:18 a.m.
NED2 Entity disambiguation (via description) batch_6a28e63ed86881909fa7b74f66b30ece completed June 10, 2026, 4:21 a.m.
Created at: April 29, 2026, 8:47 p.m.