Triple

T14882737
Position Surface form Disambiguated ID Type / Status
Subject Sealdah–Ranaghat line E350039 entity
Predicate serves P98 FINISHED
Object Halisahar E168295 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: Halisahar | Statement: [Sealdah–Ranaghat line, serves, Halisahar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Halisahar
Context triple: [Sealdah–Ranaghat line, serves, Halisahar]
  • A. Halisahar chosen
    Halisahar is a town in the North 24 Parganas district of the Indian state of West Bengal, situated along the Hooghly River and forming part of the Kolkata metropolitan area.
  • B. Khaltahi
    Khaltahi is a regional dialect of the Chhattisgarhi language spoken in parts of central India.
  • C. Harnai
    Harnai is a town in Pakistan’s Balochistan province known for its coal mining and mountainous terrain.
  • D. Bhailsa
    Bhailsa is the former historical name of Vidisha, an ancient city in the central Indian state of Madhya Pradesh known for its rich archaeological and cultural heritage.
  • E. Gharapuri
    Gharapuri is the historical name of Elephanta Island near Mumbai, India, renowned for its ancient rock-cut cave temples dedicated primarily to the Hindu god Shiva.
  • 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded5e7c0e48190af2d68a71130585c completed April 15, 2026, 12:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b5af8208190a35451477ea20b03 completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 1:56 a.m.