Triple

T7976504
Position Surface form Disambiguated ID Type / Status
Subject Kopai River E185459 entity
Predicate flowsNear P350 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: [Kopai River, flowsNear, Bolpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bolpur
Context triple: [Kopai River, flowsNear, 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_69ca829851908190b4e03829353ee7c3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3bf56f688190902b95afe42635ec completed March 31, 2026, 3:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69cdc63552ec8190bbcae99d48b5f763 completed April 2, 2026, 1:28 a.m.
Created at: March 30, 2026, 5:14 p.m.