Triple

T10170920
Position Surface form Disambiguated ID Type / Status
Subject Hoklo language E235328 entity
Predicate hasAlternativeName P39 FINISHED
Object Minnan language E228715 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: Minnan language | Statement: [Hoklo language, hasAlternativeName, Minnan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minnan language
Context triple: [Hoklo language, hasAlternativeName, Minnan language]
  • A. Minnan language chosen
    Minnan language is a major Sinitic language variety of Southern Min spoken primarily in southern Fujian, Taiwan, and among overseas Chinese communities in Southeast Asia.
  • B. Mina language
    The Mina language is a Gbe language of the Niger-Congo family spoken primarily in Togo and neighboring West African regions.
  • C. Minyag language
    The Minyag language is a lesser-known Qiangic language spoken by the Minyag people in parts of western Sichuan, China.
  • D. Muinane language
    The Muinane language is an indigenous Witotoan language spoken by the Muinane people of the Colombian Amazon.
  • E. Munji language
    The Munji language is an Eastern Iranian language spoken by the Munji people in Afghanistan’s remote Munjan Valley, closely related to the Yidgha language of Pakistan.
  • 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_69ca84ceafd0819085828600e11bed6b completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdec9d36608190be78665cc3410cf2 completed April 2, 2026, 4:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69d300f7aafc8190be874efc755bd188 completed April 6, 2026, 12:40 a.m.
Created at: March 30, 2026, 9:10 p.m.