Triple

T3702523
Position Surface form Disambiguated ID Type / Status
Subject Walapai language E80812 entity
Predicate alternateName P39 FINISHED
Object Walapi language E80812 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: Walapi language | Statement: [Walapai language, alternateName, Walapi language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Walapi language
Context triple: [Walapai language, alternateName, Walapi language]
  • A. Apalaí language
    The Apalaí language is an indigenous Cariban language spoken by the Apalaí people of the Amazon region in northern Brazil.
  • B. Walapai language chosen
    The Walapai language is a Native American language of the Yuman family traditionally spoken by the Hualapai people of northwestern Arizona.
  • C. Tyap language
    Tyap language is a Plateau language of the Niger-Congo family spoken predominantly by the Atyap people in southern Kaduna State, Nigeria.
  • D. Opata language
    The Opata language is an extinct Uto-Aztecan language once spoken by the Opata people of northern Mexico, particularly in the present-day state of Sonora.
  • E. Baniwa language
    Baniwa is an Arawakan Indigenous language spoken primarily along the Rio Negro in northwestern Brazil, as well as in parts of Colombia and Venezuela.
  • 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_69ad8b1793888190a5f70e4b21dc05a1 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adc54925b48190b23d2a14ef825abc completed March 8, 2026, 6:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4cdf53190819098529d11a5a3c7a8 completed March 14, 2026, 2:54 a.m.
Created at: March 8, 2026, 3:33 p.m.