Triple

T26312464
Position Surface form Disambiguated ID Type / Status
Subject Jadavpur, Kolkata E661862 entity
Predicate hasMunicipalWard P14475 FINISHED
Object KMC Ward 98
KMC Ward 98 is an administrative municipal ward within the jurisdiction of the Kolkata Municipal Corporation, covering part of the Jadavpur area in Kolkata, India.
E1724601 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: KMC Ward 98 | Statement: [Jadavpur, Kolkata, hasMunicipalWard, KMC Ward 98]
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: KMC Ward 98
Triple: [Jadavpur, Kolkata, hasMunicipalWard, KMC Ward 98]
Generated description
KMC Ward 98 is an administrative municipal ward within the jurisdiction of the Kolkata Municipal Corporation, covering part of the Jadavpur area in Kolkata, 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_69ee812dacfc81908484aade9120fba9 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60eeaec388190a63c44d4765ed156 completed May 2, 2026, 2:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11aea64c80819096faec0e9369f8f5 completed May 23, 2026, 1:41 p.m.
NEDg Description generation batch_6a11afe7f1f0819097ec0208368b6409 completed May 23, 2026, 1:47 p.m.
NED2 Entity disambiguation (via description) batch_6a11b0a521b08190bfda23906722482c completed May 23, 2026, 1:50 p.m.
Created at: April 26, 2026, 10:23 p.m.