Triple

T14377991
Position Surface form Disambiguated ID Type / Status
Subject Sámi languages E356523 entity
Predicate hasMemberLanguage P7390 FINISHED
Object Akkala Sámi E364673 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: Akkala Sámi | Statement: [Sámi languages, hasMemberLanguage, Akkala Sámi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akkala Sámi
Context triple: [Sámi languages, hasMemberLanguage, Akkala Sámi]
  • A. Akkala Sami chosen
    Akkala Sami is an extinct Uralic language once spoken by the Sami people in the Akkala region of northwestern Russia.
  • B. Inari Sámi
    Inari Sámi is a Uralic minority language spoken primarily around Lake Inari in northern Finland by the Inari Sámi people.
  • C. Kemi Sámi
    Kemi Sámi is an extinct Eastern Sámi language once spoken in parts of northern Finland.
  • D. Babinsky Sámi
    Babinsky Sámi is an extinct Eastern Sámi language variety that was once spoken in parts of the Kola Peninsula in Russia.
  • E. Petsamo Sámi
    Petsamo Sámi is an extinct Eastern Sámi language formerly spoken by the Sámi people in the Petsamo (Pechenga) region of northern Fennoscandia.
  • 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_69d8279163a081908aec45c0e3f1e02f completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de900a67e08190ab1dcf36e6bb3405 completed April 14, 2026, 7:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd5bc0c9708190b5025e9675e0e925 completed May 8, 2026, 3:42 a.m.
Created at: April 10, 2026, 1:16 a.m.