Triple

T21431339
Position Surface form Disambiguated ID Type / Status
Subject Nggae E528691 entity
Predicate alternativeNameOf P39 FINISHED
Object Ghari language 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: Ghari language | Statement: [Nggae, alternativeNameOf, Ghari language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ghari language
Context triple: [Nggae, alternativeNameOf, Ghari language]
  • A. Ghari language chosen
    The Ghari language is an Oceanic language spoken in the Solomon Islands, closely related to and geographically adjacent to the Gela language.
  • B. Ghomara language
    The Ghomara language is a lesser-known Berber language spoken by the Ghomara people in northern Morocco.
  • C. Kharia language
    Kharia language is a Munda language spoken primarily by the Kharia people in eastern India, especially in the states of Jharkhand, Odisha, and Chhattisgarh.
  • D. Belhare language
    The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
  • E. Baigani language
    Baigani language is an indigenous Indo-Aryan language spoken by the Baiga people of central India, particularly in parts of Madhya Pradesh and Chhattisgarh.
  • 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_69e0c455f3688190810bc96365791b0f completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b3eb08988190b50eca911442de7c completed April 22, 2026, 11:41 a.m.
Created at: April 16, 2026, 5:49 p.m.