Triple

T18208494
Position Surface form Disambiguated ID Type / Status
Subject Lamproba E435966 entity
Predicate languageContext P36 FINISHED
Object Svan 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: Svan language | Statement: [Lamproba, languageContext, Svan language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svan language
Context triple: [Lamproba, languageContext, Svan language]
  • A. Svan language chosen
    Svan language is a highly conservative and endangered Kartvelian language spoken by the Svan people in the Svaneti region of northwestern Georgia.
  • B. Alutor language
    The Alutor language is a critically endangered Chukotko-Kamchatkan language spoken by the Alutor people of northeastern Siberia in Russia.
  • C. Kodava language
    Kodava language is a Dravidian language spoken primarily by the Kodava (Coorg) community in the Kodagu district of Karnataka, India.
  • D. Pite Sami language
    Pite Sami language is an endangered Uralic language traditionally spoken by the Sámi people in parts of northern Sweden.
  • E. Lule Sami language
    Lule Sami language is a Uralic, Sami language spoken primarily in parts of northern Norway and Sweden by the Lule Sámi people.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e2261a848190b62a8485009f8f38 completed April 19, 2026, 2:09 p.m.
Created at: April 10, 2026, 10:32 a.m.