Triple

T22284074
Position Surface form Disambiguated ID Type / Status
Subject Min region E550811 entity
Predicate hasDialectGroup P1254 FINISHED
Object Eastern Min 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: Eastern Min | Statement: [Min region, hasDialectGroup, Eastern Min]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eastern Min
Context triple: [Min region, hasDialectGroup, Eastern Min]
  • A. Eastern Min chosen
    Eastern Min is a major branch of the Min group of Sinitic languages, spoken primarily in and around Fuzhou in China’s Fujian province.
  • B. Northern Min
    Northern Min is a group of closely related Sinitic (Chinese) dialects spoken primarily in northern Fujian province in southeastern China.
  • C. Eastern Cham
    Eastern Cham is an Austronesian language variety spoken by the Cham people of Vietnam, distinguished from Western Cham by its phonological and lexical features.
  • D. Eastern Mari
    Eastern Mari is a major Uralic language variety spoken primarily in the eastern regions of the Mari El Republic and neighboring areas of Russia.
  • E. Eastern Ou
    Eastern Ou was an ancient kingdom in what is now southeastern China, historically associated with the Yue peoples and neighboring states such as Minyue.
  • 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_69e11e44d538819097c6b8f333af3352 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15605a8448190906a0ab9ffa4260b completed April 29, 2026, 12:51 a.m.
Created at: April 16, 2026, 8:40 p.m.