Triple

T10855472
Position Surface form Disambiguated ID Type / Status
Subject Lower Amuzgo E256257 entity
Predicate hasAlternativeName P39 FINISHED
Object Lowland Amuzgo E256257 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: Lowland Amuzgo | Statement: [Lower Amuzgo, hasAlternativeName, Lowland Amuzgo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lowland Amuzgo
Context triple: [Lower Amuzgo, hasAlternativeName, Lowland Amuzgo]
  • A. Upper Amuzgo
    Upper Amuzgo is a variant of the Amuzgo language spoken by an indigenous community in southern Mexico.
  • B. Lower Amuzgo chosen
    Lower Amuzgo is a regional variety of the Amuzgo language spoken by indigenous communities in parts of southern Mexico.
  • C. Northern Amuzgo
    Northern Amuzgo is a major regional variety of the Amuzgo language spoken by indigenous Amuzgo communities in parts of southern Mexico.
  • D. Amuzgo language
    Amuzgo language is an indigenous Oto-Manguean language spoken primarily by the Amuzgo people in the states of Guerrero and Oaxaca in southern Mexico.
  • E. Lowland Mixe
    Lowland Mixe is an indigenous Mixe–Zoquean language spoken primarily in the lowland regions of Oaxaca, Mexico, by the Mixe people.
  • 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_69d6aa83d1448190a66d93c32394d21f completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d75135df24819090ce43afa3ea9b38 completed April 9, 2026, 7:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69e373d238b88190a6f44fecfb64410c completed April 18, 2026, 12:06 p.m.
Created at: April 8, 2026, 9:20 p.m.