Triple

T1419859
Position Surface form Disambiguated ID Type / Status
Subject Yugtun E30199 entity
Predicate alternateName P39 FINISHED
Object Yup’ik E77504 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: Yup’ik | Statement: [Yugtun, alternateName, Yup’ik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yup’ik
Context triple: [Yugtun, alternateName, Yup’ik]
  • A. Inupiaq
    Inupiaq is an Indigenous Inuit language spoken by the Inupiat people of northern and northwestern Alaska and parts of Arctic Canada.
  • B. Alutiiq
    Alutiiq is an Indigenous language of the Alutiiq (Sugpiaq) people of south-central coastal Alaska, particularly Kodiak Island and the surrounding regions.
  • C. Yupik chosen
    The Yupik are Indigenous peoples of Alaska and Siberia known for their distinct Eskimo–Aleut languages, subsistence hunting and fishing traditions, and rich Arctic cultural heritage.
  • D. Tlingit
    Tlingit is an Indigenous language of the Pacific Northwest Coast, traditionally spoken by the Tlingit people of southeastern Alaska and western Canada.
  • E. Naukan Yupik
    Naukan Yupik are an Indigenous Siberian Yupik people of the Chukotka Peninsula in Russia, with a traditional coastal hunting culture and a language closely related to that of the Alutiiq.
  • 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_69a498fb823c8190a67ce4c4837e641a completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c40764ec8190b85de6befcb20dda completed March 1, 2026, 10:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad0e6a09bc8190a9c67ec42c187340 completed March 8, 2026, 5:51 a.m.
Created at: March 1, 2026, 7:59 p.m.