Triple

T3649112
Position Surface form Disambiguated ID Type / Status
Subject Chimariko language E77374 entity
Predicate neighboringLanguage P16383 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: [Chimariko language, neighboringLanguage, Hupa language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hupa language
Context triple: [Chimariko language, neighboringLanguage, Hupa language]
  • A. Hupa language chosen
    The Hupa language is an Athabaskan language traditionally spoken by the Hupa people of northwestern California.
  • B. Walapai language
    The Walapai language is a Native American language of the Yuman family traditionally spoken by the Hualapai people of northwestern Arizona.
  • C. Tariana language
    The Tariana language is an endangered Arawakan language spoken in the northwest Amazon region of Brazil, known for its complex verbal morphology and extensive system of evidentiality.
  • D. Yavapai language
    The Yavapai language is an indigenous Native American language traditionally spoken by the Yavapai people of central and western Arizona.
  • E. Tataviam language
    The Tataviam language is an extinct Uto-Aztecan language once spoken by the Tataviam people in what is now Southern California.
  • 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_69ad85de1b988190a45f8dbfebc806fc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc38c22548190a271a69fb832a5a8 completed March 8, 2026, 6:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69b44f3c85348190b1d16179294f7f09 completed March 13, 2026, 5:54 p.m.
Created at: March 8, 2026, 3:24 p.m.