Triple

T7735862
Position Surface form Disambiguated ID Type / Status
Subject Bajawa language E175377 entity
Predicate hasNeighboringLanguage P16383 FINISHED
Object Lio language E174815 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: Lio language | Statement: [Bajawa language, hasNeighboringLanguage, Lio language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lio language
Context triple: [Bajawa language, hasNeighboringLanguage, Lio language]
  • A. Lio language chosen
    Lio language is an Austronesian language spoken by the Lio people on Flores Island in Indonesia.
  • B. Loniu language
    The Loniu language is an Oceanic language spoken on Loniu Island in Manus Province, Papua New Guinea.
  • C. Sio language
    The Sio language is an Austronesian language spoken by coastal communities in Morobe Province of Papua New Guinea, belonging to the Huon Gulf subgroup.
  • D. Lifu language
    Lifu language is an Austronesian language spoken on Lifou Island in New Caledonia, more widely known as Drehu.
  • E. Lusei language
    The Lusei language is a Kuki-Chin language of the Tibeto-Burman family spoken primarily by the Lusei (Mizo) people in northeastern India, especially in Mizoram.
  • 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_69c6995f9c60819092e386192bd63c6f completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c7033afbb881909b7ed2cc8f6c27c3 completed March 27, 2026, 10:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8be355e04819088598b5c7d61b848 completed March 29, 2026, 5:52 a.m.
Created at: March 27, 2026, 4:06 p.m.