Triple
T13448280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lule Sami |
E320541
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Pite Sami |
E81462
|
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: Pite Sami | Statement: [Lule Sami, closelyRelatedTo, Pite Sami]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pite Sami Context triple: [Lule Sami, closelyRelatedTo, Pite Sami]
-
A.
Pite Sámi
chosen
Pite Sámi is an endangered Uralic language traditionally spoken by the Sámi people in the Arjeplog area of northern Sweden.
-
B.
Kemi Sámi
Kemi Sámi is an extinct Eastern Sámi language once spoken in parts of northern Finland.
-
C.
Babinsky Sámi
Babinsky Sámi is an extinct Eastern Sámi language variety that was once spoken in parts of the Kola Peninsula in Russia.
-
D.
Lule Sámi
Lule Sámi is a Uralic, Indigenous Sámi language spoken primarily in northern Sweden and Norway.
-
E.
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.
- 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_69dbaef758b08190b9aa5ec7082cd417 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d37b9988190b8f830fb52586340 |
completed | May 3, 2026, 7:08 p.m. |
Created at: April 9, 2026, 9:41 p.m.