Triple

T35690553
Position Surface form Disambiguated ID Type / Status
Subject Ubľa E1031275 entity
Predicate governedBy P46 FINISHED
Object municipal council of Ubľa
The municipal council of Ubľa is the local representative governing body responsible for decision-making and administration in the village of Ubľa, Slovakia.
E2150787 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: municipal council of Ubľa | Statement: [Ubľa, governedBy, municipal council of Ubľa]
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: municipal council of Ubľa
Triple: [Ubľa, governedBy, municipal council of Ubľa]
Generated description
The municipal council of Ubľa is the local representative governing body responsible for decision-making and administration in the village of Ubľa, Slovakia.

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_69f76e0c73ec819080ab60a9e2f5f1f6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a07d260c819090260687cc06fa87 completed May 3, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38729104048190b20cdefbebc27fe0 completed June 21, 2026, 11:24 p.m.
NEDg Description generation batch_6a38736fdc8c8190851a4bf796f0ae6a completed June 21, 2026, 11:27 p.m.
NED2 Entity disambiguation (via description) batch_6a3873d8350481909cad8417a8427e86 completed June 21, 2026, 11:29 p.m.
Created at: May 3, 2026, 4:05 p.m.