Triple

T12749238
Position Surface form Disambiguated ID Type / Status
Subject Tai Yai E304686 entity
Predicate language P15 FINISHED
Object Shan language E304687 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: Shan language | Statement: [Tai Yai, language, Shan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shan language
Context triple: [Tai Yai, language, 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 (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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96bd75f508190aaae0969f33d1523 completed April 10, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69f67c964c508190b4d6a094b388280b completed May 2, 2026, 10:37 p.m.
Created at: April 9, 2026, 5:27 p.m.