Triple
T11970648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subarnarekha River |
E284908
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Tamluk |
E162680
|
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: Tamluk | Statement: [Subarnarekha River, nearCity, Tamluk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tamluk Context triple: [Subarnarekha River, nearCity, Tamluk]
-
A.
Tamluk
chosen
Tamluk is a historic town in eastern India known as an ancient port city and administrative center in the Purba Medinipur district of West Bengal.
-
B.
Illambazar
Illambazar is a town and administrative unit in the Birbhum district of West Bengal, India, known historically as a trading center and for its cultural and rural surroundings.
-
C.
Chanditala
Chanditala is a town in West Bengal, India, known as a suburban locality within the Kolkata metropolitan region.
-
D.
Gobardanga
Gobardanga is a town in the Indian state of West Bengal known for its suburban character and connectivity to Kolkata via the Sealdah–Bangaon railway line.
-
E.
Kumarghat
Kumarghat is a town in the Indian state of Tripura, known as a local commercial and transport hub in the Unakoti district.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48a9628cc819095d15fd90023e57d |
completed | May 1, 2026, 11:12 a.m. |
Created at: April 8, 2026, 9:46 p.m.