Triple

T18202939
Position Surface form Disambiguated ID Type / Status
Subject Guerrero region E435834 entity
Predicate languageSpoken P151 FINISHED
Object Amuzgo 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: Amuzgo language | Statement: [Guerrero region, languageSpoken, Amuzgo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amuzgo language
Context triple: [Guerrero region, languageSpoken, Amuzgo language]
  • A. Amuzgo language chosen
    Amuzgo language is an indigenous Oto-Manguean language spoken primarily by the Amuzgo people in the states of Guerrero and Oaxaca in southern Mexico.
  • B. 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.
  • C. Mayaimi language
    The Mayaimi language was the now-extinct indigenous language once spoken by the Mayaimi people around Lake Okeechobee in southern Florida.
  • D. Piapoco language
    The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
  • E. Huambisa language
    The Huambisa language is an indigenous Jivaroan language spoken by the Huambisa (Wampis) people of the northern Peruvian Amazon.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e220dca48190b54dabbd3c7c99b7 completed April 19, 2026, 2:09 p.m.
Created at: April 10, 2026, 10:32 a.m.