Triple
T12630601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalka |
E301628
|
entity |
| Predicate | nearbyHillStation |
P19493
|
FINISHED |
| Object | Kasauli |
E380304
|
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: Kasauli | Statement: [Kalka, nearbyHillStation, Kasauli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kasauli Context triple: [Kalka, nearbyHillStation, Kasauli]
-
A.
Kasauli
chosen
Kasauli is a small, picturesque hill station in the Indian state of Himachal Pradesh, known for its colonial-era architecture, pine forests, and tranquil atmosphere.
-
B.
Kullu
Kullu is a picturesque town in northern India’s Himalayas, known for its scenic valley, adventure tourism, and vibrant Dussehra festival.
-
C.
Basohli
Basohli is a historic town in Jammu and Kashmir, India, renowned as the birthplace of the bold, vibrant Basohli school of Pahari miniature painting.
-
D.
Nurpur
Nurpur is a historic town in the Kangra district of Himachal Pradesh, India, known for its ancient fort and temples amid scenic Himalayan foothills.
-
E.
Bilaspuri
Bilaspuri is an Indo-Aryan language spoken primarily in the Bilaspur region of Himachal Pradesh in northern India.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9610ce9e48190a496824002c0d2be |
completed | April 10, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684daedc88190adc403f27a850b7a |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 9, 2026, 5:15 p.m.