Triple

T15811171
Position Surface form Disambiguated ID Type / Status
Subject Kolt Saami E383356 entity
Predicate closelyRelatedTo P37 FINISHED
Object Kildin Sámi E81317 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: Kildin Sámi | Statement: [Kolt Saami, closelyRelatedTo, Kildin Sámi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kildin Sámi
Context triple: [Kolt Saami, closelyRelatedTo, Kildin Sámi]
  • A. Kildin Sámi chosen
    Kildin Sámi is a Uralic language spoken by the Sámi people primarily on Russia’s Kola Peninsula.
  • B. Pite Sámi
    Pite Sámi is an endangered Uralic language traditionally spoken by the Sámi people in the Arjeplog area of northern Sweden.
  • C. Lule Sámi
    Lule Sámi is a Uralic, Indigenous Sámi language spoken primarily in northern Sweden and Norway.
  • D. North Sámi
    North Sámi is a Uralic language spoken by the Sámi people of northern Norway, Sweden, and Finland, and is the most widely used of the Sámi languages.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b52aae14819091de08630e7e1d1a completed April 16, 2026, 10:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00580789c08190994c5c71525aadc6 completed May 10, 2026, 10:03 a.m.
Created at: April 10, 2026, 4:49 a.m.