Triple

T3796115
Position Surface form Disambiguated ID Type / Status
Subject Diegueño language E89773 entity
Predicate hasDialect P4251 FINISHED
Object Tipai E73018 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: Tipai | Statement: [Diegueño language, hasDialect, Tipai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tipai
Context triple: [Diegueño language, hasDialect, Tipai]
  • A. Tipai chosen
    Tipai is a Yuman language variety traditionally spoken by the Tipai people of northern Baja California and southern California, closely related to other Kumeyaay dialects.
  • B. Tayasan
    Tayasan is a coastal municipality in the province of Negros Oriental in the Philippines, known for its rural communities and agricultural economy.
  • C. Tai
    Tai is a major language family of Southeast Asia that includes languages such as Thai and Lao, spoken by tens of millions of people across the region.
  • D. Tai
    Tai is an ethnic subgroup of the Ogoni people in Nigeria, known for its distinct cultural identity within the broader Ogoni community.
  • E. Tiu
    Tiu is a variant transliteration of the Chinese surname commonly rendered in English as Zhao.
  • 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_69aed9597d6881909b6ee3b9de859223 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aee79f09bc8190b7514a11a030eba5 completed March 9, 2026, 3:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4fb232650819089feed9d5bb8c91a completed March 14, 2026, 6:07 a.m.
Created at: March 9, 2026, 3:15 p.m.