Triple

T4106283
Position Surface form Disambiguated ID Type / Status
Subject Guarijío E88457 entity
Predicate relatedTo P37 FINISHED
Object Mayo language E313516 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: Mayo language | Statement: [Guarijío, relatedTo, Mayo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mayo language
Context triple: [Guarijío, relatedTo, Mayo language]
  • A. Mayo language chosen
    The Mayo language is an indigenous Uto-Aztecan language spoken primarily by the Mayo people of northern Mexico, especially in the states of Sonora and Sinaloa.
  • B. Maiwa language
    The Maiwa language is an Austronesian language spoken by the Maiwa people in South Sulawesi, Indonesia.
  • C. Marau language
    The Marau language is an Oceanic language spoken in the Solomon Islands, belonging to the Southeast Solomonic branch of the Austronesian language family.
  • D. Mampruli language
    Mampruli is a Gur language spoken primarily by the Mamprusi people in northern Ghana and parts of neighboring West African countries.
  • E. Makushi language
    The Makushi language is an indigenous Cariban language spoken primarily by the Makushi people in northern Brazil and southern Guyana.
  • 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_69aed9484fb881909146f4c772ad277c completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af019c7a3c8190a503ce80e87dc3b3 completed March 9, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b56b7f88948190b87242e706a488c0 completed March 14, 2026, 2:06 p.m.
Created at: March 9, 2026, 3:40 p.m.