Triple

T7250892
Position Surface form Disambiguated ID Type / Status
Subject Moxo language E157596 entity
Predicate alternateName P39 FINISHED
Object Moxos language E157596 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: Moxos language | Statement: [Moxo language, alternateName, Moxos language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moxos language
Context triple: [Moxo language, alternateName, Moxos language]
  • A. Piapoco language
    The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
  • B. Moxo language chosen
    The Moxo language is an indigenous Arawakan language spoken by the Moxo (Mojo) people of Bolivia’s lowland regions.
  • C. Guarijío language
    The Guarijío language is an indigenous Uto-Aztecan language spoken by the Guarijío people of northern Mexico, particularly in the states of Chihuahua and Sonora.
  • D. Boruca language
    The Boruca language is an endangered indigenous Chibchan language spoken by the Boruca people of southern Costa Rica.
  • E. Sipakapense language
    The Sipakapense language is a Mayan language spoken by the Sipakapense people in the western highlands of Guatemala.
  • 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_69c6882d81d4819085f7ff862951ee4f completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea791fec8190aee56ab4503770be completed March 27, 2026, 8:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7d3a7502081909d2a97a60cc445ae completed March 28, 2026, 1:12 p.m.
Created at: March 27, 2026, 2:56 p.m.