Triple
T20213462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howrah–Sahibganj loop |
E493550
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Nalhati |
E581627
|
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: Nalhati | Statement: [Howrah–Sahibganj loop, servesCity, Nalhati]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nalhati Context triple: [Howrah–Sahibganj loop, servesCity, Nalhati]
-
A.
Nalhati
chosen
Nalhati is a town in the Birbhum district of West Bengal, India, known for its religious significance and regional marketplace.
-
B.
Lohaghat
Lohaghat is a small hill town and popular scenic destination in Uttarakhand’s Kumaon region, known for its tranquil atmosphere and views of the surrounding Himalayas.
-
C.
Bhatapara
Bhatapara is a regional dialect of the Chhattisgarhi language spoken in and around the town of Bhatapara in the Indian state of Chhattisgarh.
-
D.
Bhatapara
Bhatapara is a town and municipal council in the Baloda Bazar-Bhatapara district of Chhattisgarh, India, known primarily as a regional commercial and railway hub.
-
E.
Lalmonirhat
Lalmonirhat is a northern Bangladeshi town that serves as the administrative center of Lalmonirhat District in the Rangpur region.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed6fe888190b553ba6879cb2d8d |
completed | April 20, 2026, 6:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08551bd4d481908ef9181531c57beb |
completed | May 16, 2026, 11:29 a.m. |
Created at: April 11, 2026, 11:38 p.m.