Triple

T13448221
Position Surface form Disambiguated ID Type / Status
Subject Ter Sámi E320540 entity
Predicate branch P889 FINISHED
Object Eastern Sami E399980 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: Eastern Sami | Statement: [Ter Sámi, branch, Eastern Sami]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eastern Sami
Context triple: [Ter Sámi, branch, Eastern Sami]
  • A. Eastern Sami chosen
    Eastern Sami is a subgroup of the Sami languages spoken in northeastern Fennoscandia and northwestern Russia, characterized by several highly endangered and moribund varieties.
  • B. Western Northern Sami
    Western Northern Sami is a regional variety of the Northern Sami language spoken in the western parts of its traditional Sámi area.
  • 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. Southern Sami language
    Southern Sami is an endangered Uralic (Sami) language spoken by the Southern Sami people in parts of Norway and 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_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_69f7462340548190b156a8213f5e2556 completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:41 p.m.