Triple

T16708120
Position Surface form Disambiguated ID Type / Status
Subject North Sámi E406024 entity
Predicate closelyRelatedTo P37 FINISHED
Object Lule Sámi E393292 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: Lule Sámi | Statement: [North Sámi, closelyRelatedTo, Lule Sámi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lule Sámi
Context triple: [North Sámi, closelyRelatedTo, Lule Sámi]
  • A. Lule Sámi chosen
    Lule Sámi is a Uralic, Indigenous Sámi language spoken primarily in northern Sweden and Norway.
  • B. Southern Lule Sámi
    Southern Lule Sámi is a regional variety of the Lule Sámi language traditionally spoken by Sámi communities in the southern part of the Lule Sámi area of northern Scandinavia.
  • C. 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.
  • D. Northern Ume Sami
    Northern Ume Sami is a regional variety of the Ume Sami language traditionally spoken by Sámi communities in parts of northern Sweden.
  • E. 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.
  • 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_69d8838db21081909589220fd71440a4 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e38337ecac8190bc4a9410ed7681ab completed April 18, 2026, 1:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c79657ec8190b1b3500b7a99df0a completed May 10, 2026, 5:59 p.m.
Created at: April 10, 2026, 5:20 a.m.