Triple

T9693515
Position Surface form Disambiguated ID Type / Status
Subject Keresan languages E234592 entity
Predicate hasPart P35 FINISHED
Object Western Keres E486073 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: Western Keres | Statement: [Keresan languages, hasPart, Western Keres]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Western Keres
Context triple: [Keresan languages, hasPart, Western Keres]
  • A. Western Keres chosen
    Western Keres is a Keresan Puebloan language spoken by the Keres people of western New Mexico.
  • B. Eastern Keres
    Eastern Keres is a Keresan Puebloan language traditionally spoken by Native American communities in central New Mexico.
  • C. Western Rarámuri
    Western Rarámuri is a principal regional variety of the Rarámuri (Tarahumara) language spoken by Indigenous communities in the Sierra Madre region of northern Mexico.
  • D. Southern Numic
    Southern Numic is a branch of the Numic group of Uto-Aztecan languages spoken in parts of the southwestern United States.
  • E. Pacific Coast Athabaskan
    Pacific Coast Athabaskan refers to a group of Athabaskan (Dene) languages traditionally spoken along the Pacific coast of northwestern California and southwestern Oregon.
  • 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9d0727908190897894151c0ee7c2 completed April 1, 2026, 10:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1911d33f081908637cbf4c1949bcd completed April 4, 2026, 10:30 p.m.
Created at: March 30, 2026, 8:17 p.m.