Triple

T18538398
Position Surface form Disambiguated ID Type / Status
Subject Midnapore railway station E453023 entity
Predicate connectsTo P845 FINISHED
Object Bankura NE NERFINISHED

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: Bankura | Statement: [Midnapore railway station, connectsTo, Bankura]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bankura
Context triple: [Midnapore railway station, connectsTo, Bankura]
  • A. Bankura chosen
    Bankura is a town in eastern India known as the administrative headquarters of Bankura district and for its terracotta temples and traditional crafts.
  • B. Beránek
    Beránek is a Czech surname and word meaning "little lamb," commonly used as a family name in Czech-speaking regions.
  • C. Hanuabada
    Hanuabada is a large traditional coastal village near Port Moresby in Papua New Guinea, known as a historic center of Motuan culture and seafaring.
  • D. Dubienka
    Dubienka is a village in eastern Poland near the Bug River, historically notable as the site of the 1792 Battle of Dubienka during the Polish–Russian War.
  • E. Budni
    Budni is a town in the Sehore district of Madhya Pradesh, India, known for its industrial presence and proximity to the Narmada River.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d387b5548190aa030dad2cb4947e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e534030bd88190b25b95305a12a0c1 completed April 19, 2026, 7:58 p.m.
Created at: April 10, 2026, 11:37 a.m.