Triple

T18434604
Position Surface form Disambiguated ID Type / Status
Subject shíshálh people E450358 entity
Predicate hasLanguage P15 FINISHED
Object sháshíshálhem 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: sháshíshálhem | Statement: [shíshálh people, hasLanguage, sháshíshálhem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: sháshíshálhem
Context triple: [shíshálh people, hasLanguage, sháshíshálhem]
  • A. sháshíshálhem chosen
    sháshíshálhem is the traditional Coast Salish language spoken by the Shíshálh (Sechelt) people of British Columbia, Canada.
  • B. shíshálh
    shíshálh refers to the Indigenous Coast Salish people whose traditional territory lies along the Sunshine Coast of British Columbia, Canada.
  • C. shíshálh swiya
    shíshálh swiya is the traditional territory and homeland of the shíshálh (Sechelt) people on British Columbia’s Sunshine Coast.
  • D. ŠA
    ŠA is the regional vehicle registration code used on license plates for the city of Šabac in Serbia.
  • E. Tushemisht
    Tushemisht is a lakeside village in southeastern Albania, known for its scenic location on the shores of Lake Ohrid near the Macedonian border.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c0bd35c8190b66d62ad9987377f completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:28 a.m.