Triple
T14882738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sealdah–Ranaghat line |
E350039
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Kanchrapara |
E186001
|
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: Kanchrapara | Statement: [Sealdah–Ranaghat line, serves, Kanchrapara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kanchrapara Context triple: [Sealdah–Ranaghat line, serves, Kanchrapara]
-
A.
Kanchrapara
chosen
Kanchrapara is a town in the North 24 Parganas district of West Bengal, India, known historically for its railway workshop and suburban connectivity to Kolkata.
-
B.
Bhatapara
Bhatapara is a regional dialect of the Chhattisgarhi language spoken in and around the town of Bhatapara in the Indian state of Chhattisgarh.
-
C.
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.
-
D.
Barwadih
Barwadih is a small town in Jharkhand, India, known primarily as a local access point to the Palamau Tiger Reserve.
-
E.
Lakdikapul
Lakdikapul is a prominent commercial and transit locality in central Hyderabad, known for its busy roads, hotels, and connectivity to major city hubs.
- 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_69feae005644819098937cedb53202c5 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 1:56 a.m.