Triple

T6786759
Position Surface form Disambiguated ID Type / Status
Subject Bel languages E155826 entity
Predicate hasMember P10 FINISHED
Object Siar-Lak language E619304 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: Siar-Lak language | Statement: [Bel languages, hasMember, Siar-Lak language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Siar-Lak language
Context triple: [Bel languages, hasMember, Siar-Lak language]
  • A. Siar-Lak language chosen
    The Siar-Lak language is an Oceanic Austronesian language spoken in Papua New Guinea, primarily by communities in the New Ireland region.
  • B. Lak language
    The Lak language is a Northeast Caucasian language spoken primarily by the Lak people in the Republic of Dagestan in the North Caucasus region of Russia.
  • C. Bariai language
    The Bariai language is an Austronesian language spoken by the Bariai people of New Britain in Papua New Guinea.
  • D. Laka language
    Laka language is a lesser-known Adamawa–Ubangi language spoken in parts of Central Africa, particularly in Chad and neighboring regions.
  • E. Isnag language
    The Isnag language is an Austronesian language spoken by the Isnag people in the northern Cordillera region of Luzon in 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_69c6881770fc8190972b2906390380f5 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d28f043081909a9a9ab635785933 completed March 27, 2026, 6:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69c723cc35cc8190b5affdfd363171ba completed March 28, 2026, 12:41 a.m.
Created at: March 27, 2026, 2:14 p.m.