Triple

T14148959
Position Surface form Disambiguated ID Type / Status
Subject Tagish E350623 entity
Predicate hasNeighboringLanguage P16383 FINISHED
Object Tlingit E9440 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: Tlingit | Statement: [Tagish, hasNeighboringLanguage, Tlingit]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tlingit
Context triple: [Tagish, hasNeighboringLanguage, Tlingit]
  • A. Tlingit chosen
    Tlingit is an Indigenous language of the Pacific Northwest Coast, traditionally spoken by the Tlingit people of southeastern Alaska and western Canada.
  • B. Athabaskan–Eyak–Tlingit
    Athabaskan–Eyak–Tlingit is a proposed Native North American language family grouping that links the Athabaskan languages, Eyak, and Tlingit into a single genetic unit.
  • C. Alutiiq
    Alutiiq is an Indigenous language of the Alutiiq (Sugpiaq) people of south-central coastal Alaska, particularly Kodiak Island and the surrounding regions.
  • D. Inupiaq
    Inupiaq is an Indigenous Inuit language spoken by the Inupiat people of northern and northwestern Alaska and parts of Arctic Canada.
  • E. Eyak language
    The Eyak language is an extinct Na-Dené language once spoken by the Eyak people of south-central Alaska, now primarily documented through linguistic records and revitalization efforts.
  • 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_69d827865f608190b311820428ae027b completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61237ef481909374c1f68a2370b7 completed April 14, 2026, 3:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd2802ba608190849313ff2661cd07 completed May 8, 2026, 12:02 a.m.
Created at: April 10, 2026, 12:55 a.m.