Triple

T22934191
Position Surface form Disambiguated ID Type / Status
Subject Bada (Indonesia) E569532 entity
Predicate hasNeighborLanguage P16383 FINISHED
Object Behoa 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: Behoa language | Statement: [Bada (Indonesia), hasNeighborLanguage, Behoa language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Behoa language
Context triple: [Bada (Indonesia), hasNeighborLanguage, Behoa language]
  • A. Behoa language chosen
    The Behoa language is an Austronesian language spoken in Central Sulawesi, Indonesia, known for its place within the Badaic subgroup of the Kaili–Pamona languages.
  • B. Chambeali language
    Chambeali is an Indo-Aryan language spoken in the Chamba region of Himachal Pradesh in northern India.
  • C. Guahibo language
    The Guahibo language is an indigenous Guahiban language spoken primarily by the Guahibo people of Colombia and Venezuela.
  • D. Tembe language
    The Tembe language is an indigenous Tupi-Guarani language spoken by the Tembé people of northern Brazil.
  • E. Huambisa language
    The Huambisa language is an indigenous Jivaroan language spoken by the Huambisa (Wampis) people of the northern Peruvian Amazon.
  • 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_69e24590862c8190858f180ad302adab completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f18134484c8190b7311606c17d058d completed April 29, 2026, 3:55 a.m.
Created at: April 17, 2026, 3:44 p.m.