Triple

T13432828
Position Surface form Disambiguated ID Type / Status
Subject Eastern Sámi languages E320154 entity
Predicate hasMember P10 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: [Eastern Sámi languages, hasMember, Akkala Sámi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Akkala Sámi
Context triple: [Eastern Sámi languages, hasMember, 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. Lule Sami
    Lule Sami is a Uralic, Sami language traditionally spoken by the Lule Sámi people in parts of northern Sweden and Norway.
  • D. Kildin Sámi
    Kildin Sámi is a Uralic language spoken by the Sámi people primarily on Russia’s Kola Peninsula.
  • E. Lule Sámi
    Lule Sámi is a Uralic, Indigenous Sámi language spoken primarily in northern Sweden and Norway.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaed41a5481908800033303224adb completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7547880d48190af9b30e4e521a952 completed May 3, 2026, 1:58 p.m.
Created at: April 9, 2026, 9:40 p.m.