Triple

T14175061
Position Surface form Disambiguated ID Type / Status
Subject Havasupai–Walapai–Yavapai E351310 entity
Predicate hasMember P10 FINISHED
Object Havasupai language E13898 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: Havasupai language | Statement: [Havasupai–Walapai–Yavapai, hasMember, Havasupai language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Havasupai language
Context triple: [Havasupai–Walapai–Yavapai, hasMember, Havasupai language]
  • A. Havasupai–Hualapai language chosen
    The Havasupai–Hualapai language is an indigenous Yuman language spoken by the Havasupai and Hualapai peoples of northwestern Arizona.
  • 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. Kumbewaha language
    The Kumbewaha language is an Austronesian language spoken in Sulawesi, Indonesia, belonging to the Wotu–Wolio subgroup.
  • D. Hupa language
    The Hupa language is an Athabaskan language traditionally spoken by the Hupa people of northwestern California.
  • E. Yavapai language
    The Yavapai language is an indigenous Native American language traditionally spoken by the Yavapai people of central and western 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61b7cc3081909f4fa371e1eae130 completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf80cdae88190ae987b49218c281d completed May 7, 2026, 8:37 p.m.
Created at: April 10, 2026, 1:02 a.m.