Triple

T34854526
Position Surface form Disambiguated ID Type / Status
Subject Malout E1004691 entity
Predicate governingBody P46 FINISHED
Object Municipal Council Malout
Municipal Council Malout is the local self-governing urban body responsible for administering and managing civic services and infrastructure in the town of Malout.
E2115397 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 Malout | Statement: [Malout, governingBody, Municipal Council Malout]
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 Malout
Triple: [Malout, governingBody, Municipal Council Malout]
Generated description
Municipal Council Malout is the local self-governing urban body responsible for administering and managing civic services and infrastructure in the town of Malout.

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_69f76dba76f0819090643cba102c41ec completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78160d3388190822ed8ff3921a8f2 completed May 3, 2026, 5:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a377958313c81908ebf5e881319888d completed June 21, 2026, 5:40 a.m.
NEDg Description generation batch_6a377a56f0fc819084db07a2722f39a0 completed June 21, 2026, 5:44 a.m.
NED2 Entity disambiguation (via description) batch_6a377af6ab048190b572cefa83ec6dda completed June 21, 2026, 5:47 a.m.
Created at: May 3, 2026, 4 p.m.