Triple
T1270026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jammu and Kashmir |
E15687
|
entity |
| Predicate | hasRegion |
P285
|
FINISHED |
| Object | Jammu |
E101158
|
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: Jammu | Statement: [Jammu and Kashmir, hasRegion, Jammu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jammu Context triple: [Jammu and Kashmir, hasRegion, Jammu]
-
A.
Jammu
chosen
Jammu is a historically significant city and region in northern India, known as the winter capital of Jammu and Kashmir and a former stronghold of Dogra rulers.
-
B.
Srinagar
Srinagar is the summer capital and largest city of Jammu and Kashmir, renowned for its picturesque Dal Lake, houseboats, and Mughal-era gardens in the Kashmir Valley.
-
C.
Shimla
Shimla is a popular hill station and the capital city of Himachal Pradesh, known for its colonial-era architecture and scenic Himalayan surroundings in northern India.
-
D.
Udhampur
Udhampur is a town in the Indian union territory of Jammu and Kashmir, known for its strategic military importance and location in the Himalayan foothills.
-
E.
Ambala
Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0691d70819088e57c78ff34af1e |
completed | March 1, 2026, 10:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aca2f49a98819083dacff7e76ad195 |
completed | March 7, 2026, 10:13 p.m. |
Created at: March 1, 2026, 7:50 p.m.