Triple

T37296033
Position Surface form Disambiguated ID Type / Status
Subject Eslöv E925804 entity
Predicate governingBody P46 FINISHED
Object Eslöv Municipal Council
Eslöv Municipal Council is the elected local government body responsible for making political decisions and overseeing municipal services in Eslöv, Sweden.
E2224414 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: Eslöv Municipal Council | Statement: [Eslöv, governingBody, Eslöv Municipal Council]
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: Eslöv Municipal Council
Triple: [Eslöv, governingBody, Eslöv Municipal Council]
Generated description
Eslöv Municipal Council is the elected local government body responsible for making political decisions and overseeing municipal services in Eslöv, Sweden.

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_69f76eb0f86c819098dee07393e69ec3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb5aea85e08190b8de961455e5bde9 completed May 6, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a406cccddc4819089cc15a8baf722f0 completed June 28, 2026, 12:37 a.m.
NEDg Description generation batch_6a40708d96448190a457a7fbb50840cf completed June 28, 2026, 12:53 a.m.
NED2 Entity disambiguation (via description) batch_6a4070dfc4d48190876dd8f3753edb1b completed June 28, 2026, 12:54 a.m.
Created at: May 3, 2026, 4:16 p.m.