Triple
T9200825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kailashahar |
E220832
|
entity |
| Predicate | nearbyCity |
P350
|
FINISHED |
| Object | Dharmanagar |
E238470
|
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: Dharmanagar | Statement: [Kailashahar, nearbyCity, Dharmanagar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dharmanagar Context triple: [Kailashahar, nearbyCity, Dharmanagar]
-
A.
Dharmanagar
chosen
Dharmanagar is a prominent town and municipal council in the North Tripura district of the Indian state of Tripura, serving as an important local commercial and administrative center.
-
B.
Krishnanagar
Krishnanagar is a historic town in eastern India known for its cultural heritage, temples, and traditional clay artistry.
-
C.
Mahendranagar
Mahendranagar is a major city in far‑western Nepal, serving as an important commercial and administrative hub near the Indian border.
-
D.
Jagatballavpur
Jagatballavpur is a town and administrative block in the Howrah district of West Bengal, India, known for its semi-urban character and proximity to the Kolkata metropolitan region.
-
E.
Bhagnagar
Bhagnagar is an alternative historical name associated with the Indian city of Hyderabad.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9429b448190a078e9cdfedd4918 |
completed | April 1, 2026, 8:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09b96f0e88190bd80594fe3f769b8 |
completed | April 4, 2026, 5:03 a.m. |
Created at: March 30, 2026, 7:25 p.m.