Triple

T15873755
Position Surface form Disambiguated ID Type / Status
Subject རྫོང་ཁ E384893 entity
Predicate hasStandardForm P103 FINISHED
Object Standard 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: Standard Dzongkha | Statement: [རྫོང་ཁ, hasStandardForm, Standard Dzongkha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Standard Dzongkha
Context triple: [རྫོང་ཁ, hasStandardForm, Standard Dzongkha]
  • A. Dzongkha chosen
    Dzongkha is a Sino-Tibetan language spoken primarily in Bhutan, where it serves as the national and administrative language.
  • B. Tsongol dialect
    The Tsongol dialect is a regional variety of the Mongolic languages spoken by Tsongol communities, preserving archaic features traceable to Proto-Mongolic.
  • C. Gyel dialect
    The Gyel dialect is a regional variety of the Berom language spoken by the Berom people of central Nigeria.
  • D. 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.
  • E. 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.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e155fc02688190b6f070882b846516 completed April 16, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa94e9b548190bec74e6d9790d241 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:51 a.m.