Triple

T13282716
Position Surface form Disambiguated ID Type / Status
Subject Lake Inari E316363 entity
Predicate languageContext P36 FINISHED
Object North Sámi E406024 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: North Sámi | Statement: [Lake Inari, languageContext, North Sámi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: North Sámi
Context triple: [Lake Inari, languageContext, North Sámi]
  • A. North Sámi chosen
    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.
  • B. Eastern Sami
    Eastern Sami is a subgroup of the Sami languages spoken in northeastern Fennoscandia and northwestern Russia, characterized by several highly endangered and moribund varieties.
  • C. Lule Sámi
    Lule Sámi is a Uralic, Indigenous Sámi language spoken primarily in northern Sweden and Norway.
  • D. 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.
  • E. Kildin Sámi
    Kildin Sámi is a Uralic language spoken by the Sámi people primarily on Russia’s Kola Peninsula.
  • 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_69d806b349908190a9a61dd9323bf153 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99047531c819087aa6406de1ddc82 completed April 11, 2026, 12:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69f70a592d748190b55129515f71e979 completed May 3, 2026, 8:42 a.m.
Created at: April 9, 2026, 9:27 p.m.