Triple

T4205829
Position Surface form Disambiguated ID Type / Status
Subject Ipai people E86180 entity
Predicate language P15 FINISHED
Object Ipai language E13261 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: Ipai language | Statement: [Ipai people, language, Ipai language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ipai language
Context triple: [Ipai people, language, Ipai language]
  • A. Ipai language chosen
    The Ipai language is a Native American language traditionally spoken by the Kumeyaay (Ipai) people of southern California and northern Baja California.
  • B. 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.
  • C. Piapoco language
    The Piapoco language is an indigenous Arawakan language spoken by the Piapoco people of Colombia and Venezuela.
  • D. Tyap language
    Tyap language is a Plateau language of the Niger-Congo family spoken predominantly by the Atyap people in southern Kaduna State, Nigeria.
  • E. Apalaí language
    The Apalaí language is an indigenous Cariban language spoken by the Apalaí people of the Amazon region in northern Brazil.
  • 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_69aed93b89f48190a31f6d57c760e42f completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af03844314819092639ed7d6ef2c6e completed March 9, 2026, 5:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69b58a1ae9708190ae0f520b402c7bb5 completed March 14, 2026, 4:17 p.m.
Created at: March 9, 2026, 3:49 p.m.