Triple

T16663981
Position Surface form Disambiguated ID Type / Status
Subject Taracahitic languages E404932 entity
Predicate hasMember P10 FINISHED
Object Mayo language E313516 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: Mayo language | Statement: [Taracahitic languages, hasMember, Mayo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mayo language
Context triple: [Taracahitic languages, hasMember, Mayo language]
  • A. Mayo language chosen
    The Mayo language is an indigenous Uto-Aztecan language spoken primarily by the Mayo people of northern Mexico, especially in the states of Sonora and Sinaloa.
  • B. Maiwa language
    The Maiwa language is an Austronesian language spoken by the Maiwa people in South Sulawesi, Indonesia.
  • C. Badimaya language
    Badimaya language is an Australian Aboriginal language traditionally spoken by the Yamatji people of Western Australia.
  • D. Mayaimi language
    The Mayaimi language was the now-extinct indigenous language once spoken by the Mayaimi people around Lake Okeechobee in southern Florida.
  • E. Muya language
    The Muya language is a lesser-known Sino-Tibetan language spoken by the Muya people in parts of Sichuan, China, noted for its complex phonology and endangered status.
  • 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_69d8838b5fbc81908c6575c132b82e80 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e37c9afd048190b73bbc9c423915ca completed April 18, 2026, 12:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0084d091e0819088a98ef4aa775d07 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:18 a.m.