Triple

T29554789
Position Surface form Disambiguated ID Type / Status
Subject Jangipur Lok Sabha constituency E749877 entity
Predicate hasAssemblySegments P63908 FINISHED
Object Raghunathganj
Raghunathganj is a legislative assembly constituency in West Bengal, India, that forms part of the Jangipur Lok Sabha parliamentary seat.
E2177437 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: Raghunathganj | Statement: [Jangipur Lok Sabha constituency, hasAssemblySegments, Raghunathganj]
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: Raghunathganj
Triple: [Jangipur Lok Sabha constituency, hasAssemblySegments, Raghunathganj]
Generated description
Raghunathganj is a legislative assembly constituency in West Bengal, India, that forms part of the Jangipur Lok Sabha parliamentary seat.

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_69f0bd4919e48190942b2a13d5b97d03 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69f66d18c050819094ae0fdec7667e39 completed May 2, 2026, 9:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a396de56a948190be129bdd0f17886e completed June 22, 2026, 5:16 p.m.
NEDg Description generation batch_6a396fcd684081908c94994bf00ac889 completed June 22, 2026, 5:24 p.m.
NED2 Entity disambiguation (via description) batch_6a397038b4e0819099c71a867a5d5f40 completed June 22, 2026, 5:26 p.m.
Created at: April 28, 2026, 5:15 p.m.