Triple
T686012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haryana |
E13284
|
entity |
| Predicate | bordersState |
P224
|
FINISHED |
| Object | Uttarakhand |
E30961
|
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: Uttarakhand | Statement: [Haryana, bordersState, Uttarakhand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uttarakhand Context triple: [Haryana, bordersState, Uttarakhand]
-
A.
Uttarakhand
chosen
Uttarakhand is a northern Indian state in the Himalayas known for its sacred rivers, pilgrimage sites, and mountainous landscapes.
-
B.
Himachal Pradesh
Himachal Pradesh is a mountainous state in northern India known for its Himalayan landscapes, hill stations, and tourism.
-
C.
Garhwal
Garhwal is a mountainous cultural region in the Indian Himalayas, known for its Garhwali heritage, pilgrimage sites, and scenic landscapes in present-day Uttarakhand.
-
D.
Jammu and Kashmir
Jammu and Kashmir is a northern region of the Indian subcontinent known for its mountainous terrain, strategic location, and long-standing political and territorial disputes.
-
E.
Rajasthan
Rajasthan is a northwestern Indian state known for its vast Thar Desert, historic Rajput forts and palaces, and rich cultural heritage.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0924dec8190bbbd2bb244f85211 |
completed | March 1, 2026, 8:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acb2ede6208190ba0857f4b0209fcf |
completed | March 7, 2026, 11:21 p.m. |
Created at: March 1, 2026, 7:36 p.m.