Triple
T15345749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sametinget |
E366911
|
entity |
| Predicate | languageOfWorkOrName |
P15
|
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: [Sametinget, languageOfWorkOrName, Lule Sámi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lule Sámi Context triple: [Sametinget, languageOfWorkOrName, 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.
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.
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.
-
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.
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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e1749bc8190a8b9cbcb27288a5b |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb0319f248190a37c9afa09c32428 |
completed | May 9, 2026, 10:07 p.m. |
Created at: April 10, 2026, 3:17 a.m.