Triple

T21771842
Position Surface form Disambiguated ID Type / Status
Subject Otomi language E537451 entity
Predicate hasDialects P4251 FINISHED
Object Acazulco Otomi 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: Acazulco Otomi | Statement: [Otomi language, hasDialects, Acazulco Otomi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Acazulco Otomi
Context triple: [Otomi language, hasDialects, Acazulco Otomi]
  • A. Acazulco Otomi chosen
    Acazulco Otomi is a variant of the Otomi language spoken by the Otomi people in the community of San Jerónimo Acazulco in central Mexico.
  • B. Malacateco
    Malacateco is a professional Guatemalan football club that competes in the country’s top-tier league.
  • C. Tenango Otomi
    Tenango Otomi is a variant of the Otomi language spoken in parts of central Mexico, distinguished by its unique phonology and grammar within the Otomian language family.
  • D. Texcatepec Otomi
    Texcatepec Otomi is a regional variety of the Otomi language spoken by indigenous communities in and around Texcatepec in central Mexico.
  • E. Tilhuitlán Otomi
    Tilhuitlán Otomi is a regional variety of the Otomi language spoken by indigenous communities in and around Tilhuitlán in central Mexico.
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f031aea8c88190b4bc57df6f269ba6 completed April 28, 2026, 4:03 a.m.
Created at: April 16, 2026, 6:51 p.m.