Triple

T15655316
Position Surface form Disambiguated ID Type / Status
Subject Mordvinic languages E376423 entity
Predicate hasMember P10 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: [Mordvinic languages, hasMember, Moksha language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moksha language
Context triple: [Mordvinic languages, hasMember, 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. Mota language
    Mota language is an Oceanic language of Vanuatu historically notable as an early Christian mission lingua franca in the region.
  • C. Momo languages
    Momo languages are a small subgroup of Bantoid languages spoken in western Cameroon, closely related to other Grassfields languages.
  • D. Moxo language
    The Moxo language is an indigenous Arawakan language spoken by the Moxo (Mojo) people of Bolivia’s lowland regions.
  • E. Molbog language
    The Molbog language is an Austronesian language spoken by the Molbog people of southern Palawan in the Philippines and parts of northern Borneo.
  • 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_69d85cd1564c8190991adda63bfab4b0 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ef1f83c8190bbf65eed162cbd55 completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff6ed4d9f88190b7e24bf84c5a916f completed May 9, 2026, 5:28 p.m.
Created at: April 10, 2026, 4:15 a.m.