Triple

T7027987
Position Surface form Disambiguated ID Type / Status
Subject Bima–Sumba group E163196 entity
Predicate hasMemberLanguage P7390 FINISHED
Object Lamboya language E160651 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: Lamboya language | Statement: [Bima–Sumba group, hasMemberLanguage, Lamboya language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lamboya language
Context triple: [Bima–Sumba group, hasMemberLanguage, Lamboya language]
  • A. Lamboya language chosen
    The Lamboya language is an Austronesian language spoken by the Lamboya people on the island of Sumba in eastern Indonesia.
  • B. Chambeali language
    Chambeali is an Indo-Aryan language spoken in the Chamba region of Himachal Pradesh in northern India.
  • C. Logba language
    The Logba language is a Niger-Congo language spoken by the Logba people of southeastern Ghana.
  • D. Lamaholot language
    The Lamaholot language is an Austronesian language spoken primarily in eastern Flores and nearby islands in Indonesia, known for its numerous dialects and complex verbal morphology.
  • E. Kambaata language
    The Kambaata language is a Cushitic language of the Afroasiatic family spoken primarily by the Kambaata people in southern Ethiopia.
  • 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_69c6885d691c81908cf7d31083113886 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1fee32081908eff988b18daa6d0 completed March 27, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7758c87908190bd1ddcfdccc171b5 completed March 28, 2026, 6:30 a.m.
Created at: March 27, 2026, 2:35 p.m.