Triple
T17750615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Losar |
E443101
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Spiti |
—
|
NE NERFINISHED |
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: Spiti | Statement: [Losar, region, Spiti]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spiti Context triple: [Losar, region, Spiti]
-
A.
Spiti Valley
chosen
Spiti Valley is a high-altitude, cold desert valley in the Indian Himalayas known for its stark landscapes, Buddhist monasteries, and remote, sparsely populated villages.
-
B.
Ladakh
Ladakh is a high-altitude, sparsely populated region in northern India known for its rugged mountains, Buddhist culture, and strategic location bordering Tibet and the Karakoram range.
-
C.
Kullu Pahari
Kullu Pahari is an Indo-Aryan language spoken primarily in the Kullu Valley of Himachal Pradesh in northern India.
-
D.
Una Himachal
Una Himachal is a town in the Indian state of Himachal Pradesh known for its rail connectivity and proximity to the Punjab border.
-
E.
Chamba Pahari
Chamba Pahari is an Indo-Aryan language variety spoken in and around the Chamba 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 (2 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841a401c8190ae1dc0ed7ae4cc26 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 10:10 a.m.