Triple

T22287453
Position Surface form Disambiguated ID Type / Status
Subject Hoopa Valley E550899 entity
Predicate hasIndigenousNameLanguage P21937 FINISHED
Object Hupa language E372046 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: Hupa language | Statement: [Hoopa Valley, hasIndigenousNameLanguage, Hupa language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hupa language
Context triple: [Hoopa Valley, hasIndigenousNameLanguage, Hupa language]
  • A. Hupa language chosen
    The Hupa language is an Athabaskan language traditionally spoken by the Hupa people of northwestern California.
  • B. Niimiipu language
    Niimiipu language is the Indigenous language of the Nez Perce people of the Pacific Northwest, belonging to the Sahaptian branch of the Plateau Penutian language family.
  • C. Wailaki language
    The Wailaki language is an endangered Athabaskan language traditionally spoken by the Wailaki people of northern California.
  • D. Yakama language
    The Yakama language is a Native American Sahaptin language traditionally spoken by the Yakama people of the Pacific Northwest region of the United States.
  • E. Walapai language
    The Walapai language is a Native American language of the Yuman family traditionally spoken by the Hualapai people of northwestern Arizona.
  • 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_69e11e44d538819097c6b8f333af3352 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1560896348190985725ac8ad406b3 completed April 29, 2026, 12:51 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0abcadc3e081908e98e6810b3cba6e completed May 18, 2026, 7:15 a.m.
Created at: April 16, 2026, 8:40 p.m.