Triple

T17087513
Position Surface form Disambiguated ID Type / Status
Subject Koyuk, Alaska E414636 entity
Predicate hasIndigenousLanguage P4185 FINISHED
Object Inupiaq E2449 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: Inupiaq | Statement: [Koyuk, Alaska, hasIndigenousLanguage, Inupiaq]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Inupiaq
Context triple: [Koyuk, Alaska, hasIndigenousLanguage, 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 (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_69d886cef44c8190ba56c44b4e863e64 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbe92e488190b947287a968086d5 completed April 18, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012ee81fd08190a7e1f5958fbe3b97 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:35 a.m.