Triple
T21908456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lepcha |
E541000
|
entity |
| Predicate | hasDialects |
P4251
|
FINISHED |
| Object | Dzongu Lepcha |
—
|
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: Dzongu Lepcha | Statement: [Lepcha, hasDialects, Dzongu Lepcha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dzongu Lepcha Context triple: [Lepcha, hasDialects, Dzongu Lepcha]
-
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.
Dzongsam
Dzongsam is an alternative name for Jomsom, a town in Nepal’s Mustang region that serves as a key gateway to the Annapurna and Upper Mustang trekking areas.
-
C.
Khaling Tsangla
Khaling Tsangla is a regional dialect of the Tsangla language spoken by the Khaling community in parts of the eastern Himalayas.
-
D.
Dungsam Tsangla
Dungsam Tsangla is a regional dialect of the Tsangla language spoken primarily in the Dungsam area of eastern Bhutan.
-
E.
Lepcha language
chosen
The Lepcha language is an indigenous Sino-Tibetan language spoken primarily by the Lepcha people in parts of Sikkim and neighboring regions of India, Bhutan, and Nepal, known for its unique script and rich oral tradition.
- 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_69e0c47b4e8c81908c8076eaa4c8e4f2 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121d806688190b23502aacbfde4bd |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 16, 2026, 7:39 p.m.