Triple

T12826906
Position Surface form Disambiguated ID Type / Status
Subject Ashima Ganguli E306675 entity
Predicate hasSurname P18 FINISHED
Object Ganguli E999794 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: Ganguli | Statement: [Ashima Ganguli, hasSurname, Ganguli]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ganguli
Context triple: [Ashima Ganguli, hasSurname, Ganguli]
  • A. Ganguli chosen
    Ganguli is a Bengali surname commonly associated with Indian families, notably featured in Jhumpa Lahiri’s novel "The Namesake" through the character Gogol Ganguli.
  • B. Basu
    Basu is an Indian surname, particularly common among Bengali communities, that is closely related to and sometimes used as a variant of the surname Bose.
  • C. Chattopadhyay
    Chattopadhyay is a Bengali surname notably borne by influential Indian writer Sarat Chandra Chattopadhyay, renowned for his socially conscious novels and stories.
  • D. Deukhuri
    Deukhuri is a town in southwestern Nepal that serves as the administrative center of Lumbini (Province 5).
  • E. Sengupta
    Sengupta is a common Bengali surname originating from the Indian subcontinent, traditionally associated with Bengali Hindu communities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d7bdf52b94819096d6f0ba4ab50a98 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96fae51608190a50970bd038359a5 completed April 10, 2026, 9:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f68ed4f7388190ba989b8a79bd7c6d completed May 2, 2026, 11:55 p.m.
Created at: April 9, 2026, 5:33 p.m.