Triple

T16662155
Position Surface form Disambiguated ID Type / Status
Subject Trongsa District E404884 entity
Predicate officialLanguage P236 FINISHED
Object Dzongkha E79075 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: Dzongkha | Statement: [Trongsa District, officialLanguage, Dzongkha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dzongkha
Context triple: [Trongsa District, officialLanguage, Dzongkha]
  • A. Dzongkha chosen
    Dzongkha is a Sino-Tibetan language spoken primarily in Bhutan, where it serves as the national and administrative language.
  • B. 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.
  • C. Dholuo
    Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
  • D. 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.
  • E. Gyel dialect
    The Gyel dialect is a regional variety of the Berom language spoken by the Berom people of central Nigeria.
  • 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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37c99efa8819096c6325ff4898bd7 completed April 18, 2026, 12:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084d091e0819088a98ef4aa775d07 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:18 a.m.