Triple

T1603648
Position Surface form Disambiguated ID Type / Status
Subject Hakka E34449 entity
Predicate subclassOf P1244 FINISHED
Object Hakka Chinese E34449 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: Hakka Chinese | Statement: [Hakka, subclassOf, Hakka Chinese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hakka Chinese
Context triple: [Hakka, subclassOf, Hakka Chinese]
  • A. Hakka chosen
    Hakka is a Sinitic language spoken primarily by the Hakka people across southern China and various overseas Chinese communities.
  • B. Teochew
    Teochew is a Southern Min Chinese dialect originating from the Chaoshan region of Guangdong, widely spoken in overseas Chinese communities across Southeast Asia.
  • C. Siwu language
    The Siwu language is a Niger-Congo language spoken primarily in the Volta Region of Ghana by the Mawu people.
  • D. Jiaoliao Mandarin
    Jiaoliao Mandarin is a regional variety of Mandarin Chinese spoken primarily in the Jiaodong and Liaodong peninsulas of northeastern China.
  • E. Yue Chinese
    Yue Chinese is a major branch of the Chinese language family, best known internationally through its prominent variety Cantonese spoken in southern China and among overseas Chinese communities.
  • 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_69a885fea6a481909fe83ba6441f1774 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a9094f96ec819090286c21b3dfddd5 completed March 5, 2026, 4:40 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad46ae8ef08190acf018f1db4bfa7c completed March 8, 2026, 9:51 a.m.
Created at: March 4, 2026, 7:28 p.m.