Triple

T33751651
Position Surface form Disambiguated ID Type / Status
Subject Omotic–Datooga languages E864856 entity
Predicate hasWorkingLanguageFamily P64460 FINISHED
Object Omotic LITERAL 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: Omotic | Statement: [Omotic–Datooga languages, hasWorkingLanguageFamily, Omotic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWorkingLanguageFamily
Context triple: [Omotic–Datooga languages, hasWorkingLanguageFamily, Omotic]
  • A. usesLanguageFamily
    Indicates that an entity communicates or operates using a language that belongs to a specified language family.
  • B. usesWorkingLanguagesOf
    Indicates that one entity employs or operates using the working languages associated with another entity.
  • C. isInLanguageFamily chosen
    Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
  • D. languageFamilyPresence
    Indicates that a particular language family is present or attested within a specified region, group, or context.
  • E. appliesToLanguageFamily
    Indicates that something (such as a rule, feature, or classification) is relevant or applicable to an entire language family rather than to a single language.
  • F. None of above.

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_69f3498c35f881909df279ae4270f831 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fdec5ffe088190ac5505f26c6cff18 completed May 8, 2026, 2 p.m.
PD Predicate disambiguation batch_69fdeae15f1c81908fc63fbc1b028d2e completed May 8, 2026, 1:53 p.m.
Created at: May 1, 2026, 1:45 a.m.