Triple

T25452887
Position Surface form Disambiguated ID Type / Status
Subject Barasat E637834 entity
Predicate governingBody P46 FINISHED
Object Barasat Municipality
Barasat Municipality is the local urban civic body responsible for administering and providing municipal services to the town of Barasat in West Bengal, India.
E1688344 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: Barasat Municipality | Statement: [Barasat, governingBody, Barasat 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: Barasat Municipality
Triple: [Barasat, governingBody, Barasat Municipality]
Generated description
Barasat Municipality is the local urban civic body responsible for administering and providing municipal services to the town of Barasat in West Bengal, India.

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_69e75db7c5048190b8da9cd7eeedb610 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f70885cc81909f1574406d67c682 completed May 2, 2026, 1:07 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10b739d2ac8190be2039bac6a97bdf completed May 22, 2026, 8:06 p.m.
NEDg Description generation batch_6a10b94377108190a5fb35e99b5f0351 completed May 22, 2026, 8:14 p.m.
NED2 Entity disambiguation (via description) batch_6a10b9c6dbf48190abe4efb4035db2a0 completed May 22, 2026, 8:17 p.m.
Created at: April 21, 2026, 2:03 p.m.