Triple

T19333207
Position Surface form Disambiguated ID Type / Status
Subject Lak E483549 entity
Predicate autonymLanguage P1435 FINISHED
Object Lak 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: Lak language | Statement: [Lak, autonymLanguage, Lak language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lak language
Context triple: [Lak, autonymLanguage, Lak language]
  • A. Lak language chosen
    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.
  • B. Laka language
    Laka language is a lesser-known Adamawa–Ubangi language spoken in parts of Central Africa, particularly in Chad and neighboring regions.
  • C. Lakalai language
    The Lakalai language is an Austronesian language spoken by the Lakalai people of New Britain in Papua New Guinea.
  • D. Siar-Lak language
    The Siar-Lak language is an Oceanic Austronesian language spoken in Papua New Guinea, primarily by communities in the New Ireland region.
  • E. Laki language
    The Laki language is an Iranian language spoken primarily by the Laki people of western Iran, often considered transitional between Kurdish and Luri.
  • 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_69d8e8d13e3c81909d91d1d5ec37c095 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e61642f49c81909226cfd701f7c139 completed April 20, 2026, 12:04 p.m.
Created at: April 10, 2026, 1:33 p.m.