Triple

T23320135
Position Surface form Disambiguated ID Type / Status
Subject Lan Yu Yami E591127 entity
Predicate language P15 FINISHED
Object Yami language 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: Yami language | Statement: [Lan Yu Yami, language, Yami language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yami language
Context triple: [Lan Yu Yami, language, Yami language]
  • A. Yami language chosen
    The Yami language is an Austronesian language spoken by the Tao (Yami) people of Orchid Island in Taiwan, known for preserving many archaic features within the Batanic subgroup.
  • B. Badimaya language
    Badimaya language is an Australian Aboriginal language traditionally spoken by the Yamatji people of Western Australia.
  • C. Sayawa language
    The Sayawa language is a Chadic language spoken primarily by the Sayawa people in Bauchi State, northeastern Nigeria.
  • D. Tai Yo language
    The Tai Yo language is a Southwestern Tai language spoken by the Tai Yo ethnic group in parts of Vietnam, Laos, and Thailand.
  • E. Salt-Yui language
    The Salt-Yui language is a Papuan language spoken by the Chimbu people of Papua New Guinea.
  • 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_69e25d1effe4819096907f95f610dbff completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1978440888190b316664812105d60 completed April 29, 2026, 5:30 a.m.
Created at: April 17, 2026, 5:07 p.m.