Triple
T17809718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahaul |
E444664
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Bhoti |
—
|
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: Bhoti | Statement: [Lahaul, hasLanguage, Bhoti]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhoti Context triple: [Lahaul, hasLanguage, Bhoti]
-
A.
Bhutia
Bhutia is a Sino-Tibetan language spoken primarily by the Bhutia community in the Himalayan regions of India, especially in Sikkim and parts of West Bengal.
-
B.
བལྟི (Balti)
བལྟི (Balti) refers to the Balti people, an ethnic group of Tibetan origin primarily inhabiting the Baltistan region in the northern areas of Pakistan and parts of India.
-
C.
Dholuo
Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
-
D.
Garhwali
Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
-
E.
Tibetan
chosen
Tibetan is a Sino-Tibetan language spoken primarily in Tibet and surrounding Himalayan regions, serving as the liturgical language of Tibetan Buddhism and a key marker of Tibetan cultural identity.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887a50488190b9c148146ec607e6 |
completed | April 19, 2026, 7:47 a.m. |
Created at: April 10, 2026, 10:14 a.m.