Triple
T9768227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shibpur |
E237052
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Howrah city |
E38476
|
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: Howrah city | Statement: [Shibpur, locatedIn, Howrah city]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Howrah city Context triple: [Shibpur, locatedIn, Howrah city]
-
A.
Howrah
chosen
Howrah is a major industrial city in the Indian state of West Bengal, located on the Hooghly River opposite Kolkata and known for the iconic Howrah Bridge and its busy railway junction.
-
B.
Islampur
Islampur is a town in the Indian state of West Bengal, known as a local commercial and administrative center in the northern part of the state.
-
C.
Konnagar
Konnagar is a suburban town in West Bengal, India, situated along the Hooghly River and known as part of the Kolkata metropolitan area.
-
D.
Diamond Harbour
Diamond Harbour is a town in eastern India situated along the Hooghly River, known as a gateway to the Bay of Bengal and a popular regional tourist and trading hub.
-
E.
Dispur
Dispur is a locality in Guwahati that serves as the administrative and political center of the Indian state of Assam.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a2da648190836916a45d2998d7 |
completed | April 1, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc46f170819081ecc5e85a0514c3 |
completed | April 5, 2026, 2:43 a.m. |
Created at: March 30, 2026, 8:25 p.m.