Triple

T22849540
Position Surface form Disambiguated ID Type / Status
Subject Jingpho E566319 entity
Predicate influencedBy P9 FINISHED
Object Shan language 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: Shan language | Statement: [Jingpho, influencedBy, Shan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shan language
Context triple: [Jingpho, influencedBy, Shan language]
  • A. Shan language chosen
    Shan language is a Tai-Kadai language spoken primarily by the Shan people in Myanmar, with communities also in neighboring Thailand and China.
  • B. Shina language
    Shina language is an Indo-Aryan language primarily spoken by the Shina people in the mountainous regions of northern Pakistan and parts of neighboring areas.
  • C. Chaoshan language
    The Chaoshan language is a Southern Min Chinese variety spoken primarily in the Chaoshan region of eastern Guangdong, known for its distinct phonology and strong cultural identity among Teochew and Swatow communities.
  • D. Shui language
    The Shui language is a Kam–Sui (Kra–Dai) language spoken primarily by the Shui ethnic group in Guizhou Province, China.
  • E. Rengma language
    Rengma language is a Tibeto-Burman language spoken primarily by the Rengma Naga people in the northeastern region of India.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17eb74700819090d191b3a7a17034 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.