Triple

T9229813
Position Surface form Disambiguated ID Type / Status
Subject Siksha Bhavana E221785 entity
Predicate locatedNear P294 FINISHED
Object Bolpur E135507 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: Bolpur | Statement: [Siksha Bhavana, locatedNear, Bolpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bolpur
Context triple: [Siksha Bhavana, locatedNear, Bolpur]
  • A. Bolpur chosen
    Bolpur is a town in West Bengal, India, best known as the gateway to Santiniketan, the cultural and educational hub founded by Rabindranath Tagore.
  • B. Santipur
    Santipur is a historic town in West Bengal, India, renowned for its traditional handloom sarees and cultural heritage.
  • C. Baranagar
    Baranagar is a densely populated suburban city in the northern part of Kolkata, India, known for its industrial areas, educational institutions, and cultural heritage.
  • D. Muktainagar
    Muktainagar is a town in the Jalgaon district of Maharashtra, India, known primarily as an agricultural and trading center in the region.
  • E. Sainthia
    Sainthia is a town in the Birbhum district of West Bengal, India, known as a local commercial and cultural center.
  • 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_69ca83ed628c8190bc02d641e57f097f completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccee17a2dc8190b373f78be7247f0d completed April 1, 2026, 10:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0c71e206c8190bcc0b7cee01fc765 completed April 4, 2026, 8:09 a.m.
Created at: March 30, 2026, 7:29 p.m.