Triple

T7217162
Position Surface form Disambiguated ID Type / Status
Subject Erzya language E149564 entity
Predicate closelyRelatedTo P37 FINISHED
Object Moksha language E149565 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: Moksha language | Statement: [Erzya language, closelyRelatedTo, Moksha language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moksha language
Context triple: [Erzya language, closelyRelatedTo, Moksha language]
  • A. Moksha language chosen
    The Moksha language is a Uralic language spoken primarily by the Moksha people in central Russia, noted for its complex grammar and close relation to the Erzya language.
  • B. Momo languages
    Momo languages are a small subgroup of Bantoid languages spoken in western Cameroon, closely related to other Grassfields languages.
  • C. Moxo language
    The Moxo language is an indigenous Arawakan language spoken by the Moxo (Mojo) people of Bolivia’s lowland regions.
  • D. Moghamo language
    The Moghamo language is a Bantu-related Grassfields language spoken by the Moghamo people in the Northwest Region of Cameroon.
  • E. Moru language
    The Moru language is a Central Sudanic language spoken primarily by the Moru people of South Sudan.
  • 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_69c687eca814819095abb52316b1af80 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6e99170d88190b1aef326a7d81134 completed March 27, 2026, 8:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7cbfb46388190992cc98039e71748 completed March 28, 2026, 12:39 p.m.
Created at: March 27, 2026, 2:53 p.m.