Triple

T15257091
Position Surface form Disambiguated ID Type / Status
Subject Akkala Sami E364673 entity
Predicate hasAlternativeName P39 FINISHED
Object Babinsk Sami E1050906 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: Babinsk Sami | Statement: [Akkala Sami, hasAlternativeName, Babinsk Sami]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Babinsk Sami
Context triple: [Akkala Sami, hasAlternativeName, Babinsk Sami]
  • A. Babinsky Sámi chosen
    Babinsky Sámi is an extinct Eastern Sámi language variety that was once spoken in parts of the Kola Peninsula in Russia.
  • B. Lule Sami
    Lule Sami is a Uralic, Sami language traditionally spoken by the Lule Sámi people in parts of northern Sweden and Norway.
  • C. Akkala Sami
    Akkala Sami is an extinct Uralic language once spoken by the Sami people in the Akkala region of northwestern Russia.
  • D. 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.
  • E. Kainuu Sámi
    Kainuu Sámi is an extinct Uralic language once spoken by the Sámi people in the Kainuu region of Finland.
  • 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_69d85a0f08408190b3c3259ae35d79d2 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0084b97908190b3bf7ea7bd75bdc0 completed April 15, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69fee5f7bd2081909c003deb3a692f18 completed May 9, 2026, 7:44 a.m.
Created at: April 10, 2026, 3:13 a.m.