Triple

T25304934
Position Surface form Disambiguated ID Type / Status
Subject Miryang Arirang E634455 entity
Predicate instanceOf P0 FINISHED
Object regional variant of Arirang C49998 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: regional variant of Arirang
Context triple: [Miryang Arirang, instanceOf, regional variant of Arirang]
  • A. regional variety of Ghomalaʼ
    A regional variety of Ghomalaʼ is a geographically localized dialect of the Ghomalaʼ language characterized by distinct phonological, lexical, or syntactic features specific to a particular area or community.
  • B. Southern Min variety
    A Southern Min variety is a regional form of the Southern Min (Minnan) branch of Chinese, encompassing mutually related but often not mutually intelligible dialects spoken primarily in southern Fujian, eastern Guangdong, Hainan, Taiwan, and among overseas Chinese communities.
  • C. regional variety of Toraja-Saʼdan
    A regional variety of Toraja-Saʼdan is a geographically distinct form of the Toraja-Saʼdan language characterized by unique phonological, lexical, and grammatical features specific to a particular area or community.
  • D. regional variety of Siwu language
    A regional variety of the Siwu language is a geographically and socially distinct form of Siwu characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Siwu-speaking areas.
  • E. regional variety of Jingpo language
    A regional variety of the Jingpo language is a geographically or socially distinct form of Jingpo characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Jingpo varieties.
  • F. None of above. chosen

Provenance (1 batch)

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_69e75a972c6481909bc11710e8d30a6c completed April 21, 2026, 11:08 a.m.
Created at: April 21, 2026, 1:25 p.m.