Triple

T23338027
Position Surface form Disambiguated ID Type / Status
Subject Golovin, Alaska E591651 entity
Predicate traditionalLanguage P6149 FINISHED
Object Inupiaq NE NERFINISHED

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: Inupiaq | Statement: [Golovin, Alaska, traditionalLanguage, Inupiaq]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inupiaq
Context triple: [Golovin, Alaska, traditionalLanguage, Inupiaq]
  • A. Inupiaq chosen
    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. Ahtna Athabaskan
    Ahtna Athabaskan are an Indigenous Athabaskan-speaking people of south-central Alaska whose traditional homeland centers on the Copper River basin.
  • D. Ahtna language
    The Ahtna language is an Athabaskan language traditionally spoken by the Ahtna people of south-central Alaska, particularly around the Copper River region.
  • E. Alaskan Athabaskan
    Alaskan Athabaskan is a subgroup of Northern Athabaskan Indigenous peoples and languages native to interior and southwestern Alaska.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e25d20156c81908c5c53195bd9c738 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1983099188190a2e05cf81d62a641 completed April 29, 2026, 5:33 a.m.
Created at: April 17, 2026, 5:17 p.m.