Triple

T22887859
Position Surface form Disambiguated ID Type / Status
Subject Flathead E567654 entity
Predicate hasAlternativeName P39 FINISHED
Object Salish 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: Salish | Statement: [Flathead, hasAlternativeName, Salish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salish
Context triple: [Flathead, hasAlternativeName, Salish]
  • A. Halkomelem Salish
    Halkomelem Salish is a Coast Salish Indigenous language of the Salishan family traditionally spoken in the southwestern British Columbia region of Canada.
  • B. Spokane Salish
    Spokane Salish is an Interior Salishan Indigenous language traditionally spoken by the Spokane people of the Pacific Northwest region of the United States.
  • C. Salishan languages chosen
    The Salishan languages are a family of Indigenous languages spoken by various First Nations and Native American peoples of the Pacific Northwest region of North America.
  • D. Northern Straits Salish
    Northern Straits Salish is an Indigenous Salishan language traditionally spoken by several Coast Salish communities in the Strait of Georgia and Puget Sound region of the Pacific Northwest.
  • E. Lushootseed
    Lushootseed is a Coast Salish Native American language traditionally spoken in the Puget Sound region of Washington State.
  • 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_69e2458a92ec81908fc1cd5f6407d2ab completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17fc2adb4819081bce7e6849ba31a completed April 29, 2026, 3:49 a.m.
Created at: April 17, 2026, 3:40 p.m.