Triple

T21603509
Position Surface form Disambiguated ID Type / Status
Subject Papuan languages of the Solomon Islands E533110 entity
Predicate hasMember P10 FINISHED
Object Bilua 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: Bilua language | Statement: [Papuan languages of the Solomon Islands, hasMember, Bilua language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bilua language
Context triple: [Papuan languages of the Solomon Islands, hasMember, Bilua language]
  • A. Bilua language chosen
    The Bilua language is a Papuan language spoken primarily on Vella Lavella Island in the Solomon Islands.
  • B. Bira language
    The Bira language is a Bantu language spoken by the Bira people of the eastern Democratic Republic of the Congo.
  • C. Baliledu language
    The Baliledu language is an Austronesian language of the Bima–Sumba subgroup spoken by a local community in eastern Indonesia.
  • D. Bafia language
    The Bafia language is a Bantu language spoken primarily by the Bafia people in central Cameroon.
  • E. Biwat language
    The Biwat language is a Ramu family Papuan language spoken by the Biwat (Mundugumor) people of Papua New Guinea.
  • 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_69e0c46364608190a337dc8720dc2a35 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef17e31c80819090fdd63b5c103acb completed April 27, 2026, 8:01 a.m.
Created at: April 16, 2026, 6:33 p.m.