Triple
T13895102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sambalpur Junction |
E334066
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Bilaspur |
E205384
|
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: Bilaspur | Statement: [Sambalpur Junction, connectsTo, Bilaspur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bilaspur Context triple: [Sambalpur Junction, connectsTo, Bilaspur]
-
A.
Bilaspur
chosen
Bilaspur is a major city in the Indian state of Chhattisgarh, known as an important administrative, commercial, and judicial center.
-
B.
Bilaspur
Bilaspur is a town in the Yamunanagar district of Haryana, India, known as a local commercial and administrative center for surrounding rural areas.
-
C.
Bilaspur
Bilaspur is a town in the Rampur district of Uttar Pradesh, India, known as a local commercial and administrative center for surrounding rural areas.
-
D.
Bilaspuri
Bilaspuri is an Indo-Aryan language spoken primarily in the Bilaspur region of Himachal Pradesh in northern India.
-
E.
Hamirpur
Hamirpur is a town and district headquarters in the Bundelkhand region of Uttar Pradesh, India, known for its location near the confluence of the Yamuna and Betwa rivers.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a741908190bdf46d76c5f1411a |
completed | April 14, 2026, 11:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c229f448190b7ea1a1bf9d086cf |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 9, 2026, 10:15 p.m.