Triple
T3731608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzongkha |
E79075
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Bhutanese |
E334858
|
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: Bhutanese | Statement: [Dzongkha, hasAlternativeName, Bhutanese]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhutanese Context triple: [Dzongkha, hasAlternativeName, Bhutanese]
-
A.
Bhutanese people
chosen
Bhutanese people are the native inhabitants of Bhutan, characterized by a mix of Tibetan, South Asian, and Himalayan cultural influences and a strong Buddhist heritage.
-
B.
Dzongkha
Dzongkha is a Sino-Tibetan language spoken primarily in Bhutan, where it serves as the national and administrative language.
-
C.
Tibetan
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.
-
D.
Newar
Newar are an indigenous ethnic group of the Kathmandu Valley in Nepal, known for their rich urban culture, craftsmanship, and Newar language.
-
E.
Dholuo
Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb21002c81908438170ed6f6c271 |
completed | March 8, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4db167c5881909772cf1e78717995 |
completed | March 14, 2026, 3:50 a.m. |
Created at: March 8, 2026, 3:34 p.m.