Triple
T13851493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhatapara |
E332953
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Bhatapara |
E332953
|
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: Bhatapara | Statement: [Bhatapara, spokenIn, Bhatapara]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhatapara Context triple: [Bhatapara, spokenIn, Bhatapara]
-
A.
Bhatapara
chosen
Bhatapara is a regional dialect of the Chhattisgarhi language spoken in and around the town of Bhatapara in the Indian state of Chhattisgarh.
-
B.
Kanchrapara
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.
-
C.
Bhatpara
Bhatpara is an industrial and residential town in the North 24 Parganas district of West Bengal, India, known for its jute mills and dense urban population along the Hooghly River.
-
D.
Mohanbari
Mohanbari is a locality in the Dibrugarh district of Assam, India, known primarily for hosting the Dibrugarh Airport.
-
E.
Nalhati
Nalhati is a town in the Birbhum district of West Bengal, India, known for its religious significance and regional marketplace.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02da9460819093a3ec5a3c62ea81 |
completed | April 14, 2026, 9:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fba1bbee14819082e1a381a5950e07 |
completed | May 6, 2026, 8:17 p.m. |
Created at: April 9, 2026, 10:14 p.m.