Triple

T22192394
Position Surface form Disambiguated ID Type / Status
Subject Javeriano Moxeño E548460 entity
Predicate usesLanguage P238 FINISHED
Object Moxeño 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: Moxeño language | Statement: [Javeriano Moxeño, usesLanguage, Moxeño language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moxeño language
Context triple: [Javeriano Moxeño, usesLanguage, Moxeño language]
  • A. Moxeño languages
    The Moxeño languages are a group of closely related Arawakan indigenous languages spoken by the Moxeño people of Bolivia’s Beni region.
  • B. Tepehuán language
    The Tepehuán language is a Uto-Aztecan indigenous language of northern Mexico spoken by the Tepehuán people in several regional dialects.
  • C. Moxo language chosen
    The Moxo language is an indigenous Arawakan language spoken by the Moxo (Mojo) people of Bolivia’s lowland regions.
  • D. Mocoví language
    The Mocoví language is an indigenous Guaicuruan language of the Gran Chaco region, traditionally spoken by the Mocoví people in northern Argentina.
  • E. Picurís language
    The Picurís language is a Native American Tanoan language traditionally spoken by the Picurís Pueblo people of northern New Mexico and now considered highly endangered.
  • 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_69e11e3e0c7c8190b30d278845e2497e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12ae49ec881908fa42446b19e3f2d completed April 28, 2026, 9:47 p.m.
Created at: April 16, 2026, 8:35 p.m.