Triple

T6641194
Position Surface form Disambiguated ID Type / Status
Subject Vella Lavella language E150588 entity
Predicate isRelatedTo P37 FINISHED
Object Bilua language E145900 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: Bilua language | Statement: [Vella Lavella language, isRelatedTo, Bilua language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bilua language
Context triple: [Vella Lavella language, isRelatedTo, Bilua language]
  • A. Bilua language chosen
    The Bilua language is a Papuan language spoken primarily on Vella Lavella Island in the Solomon Islands.
  • B. Baliledu language
    The Baliledu language is an Austronesian language of the Bima–Sumba subgroup spoken by a local community in eastern Indonesia.
  • C. Logba language
    The Logba language is a Niger-Congo language spoken by the Logba people of southeastern Ghana.
  • D. Kulisusu language
    The Kulisusu language is an Austronesian language spoken by the Kulisusu people of southeastern Sulawesi, Indonesia.
  • E. Kalanguya language
    The Kalanguya language is an Austronesian language spoken by the Kalanguya people in the northern Luzon highlands of the Philippines.
  • 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_69c687f1a3048190828b7342f7125d5c completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6aff42c748190b818cf55f83647cb completed March 27, 2026, 4:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cbf9c57c8190b617d21bb2b46b1e completed March 27, 2026, 6:27 p.m.
Created at: March 27, 2026, 2 p.m.