Triple

T16659044
Position Surface form Disambiguated ID Type / Status
Subject Howrah–Bardhaman main line E404809 entity
Predicate servesTown P847 FINISHED
Object Bandel E162703 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: Bandel | Statement: [Howrah–Bardhaman main line, servesTown, Bandel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bandel
Context triple: [Howrah–Bardhaman main line, servesTown, Bandel]
  • A. Bandel chosen
    Bandel is a historic town in West Bengal, India, known for its riverside location, colonial-era heritage, and the prominent Bandel Church.
  • B. Gangabai
    Gangabai was the mother of Madhav Rao II, a prominent Maratha Peshwa of the late 18th century.
  • C. Bhagyanagar
    Bhagyanagar is an old historical name for the Indian city now known as Hyderabad.
  • D. Benipatti
    Benipatti is a town in the Madhubani district of the Indian state of Bihar, known for its rural setting and proximity to the region’s famed Mithila culture.
  • E. Putalibazar
    Putalibazar is a municipality in central Nepal known as a local administrative and commercial center within Gandaki Province.
  • 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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37bfcbb6881909c0419174dd017dc completed April 18, 2026, 12:41 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084ce7cf0819091e7a4de2cc010ea completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:18 a.m.