Triple

T16772876
Position Surface form Disambiguated ID Type / Status
Subject Cucapá E407645 entity
Predicate hasNameVariant P457 FINISHED
Object Cocopa E91836 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: Cocopa | Statement: [Cucapá, hasNameVariant, Cocopa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cocopa
Context triple: [Cucapá, hasNameVariant, Cocopa]
  • A. Cochimí
    Cochimí were an Indigenous people of the Baja California Peninsula in Mexico, known for their distinct language and traditional hunter-gatherer lifestyle.
  • B. Tepehuan
    The Tepehuan are an Indigenous people of northern Mexico, known for their distinct Uto-Aztecan language, traditional agriculture, and communities in the Sierra Madre Occidental.
  • C. Mizque
    Mizque is a small historic town and agricultural center in central Bolivia, known for its colonial architecture and fertile valleys within the Cochabamba region.
  • D. Cajidiocan
    Cajidiocan is a coastal municipality located on Sibuyan Island in the province of Romblon in the Philippines.
  • E. U.S. Cocopa chosen
    U.S. Cocopa is a regional dialect of the Cocopa language spoken by Cocopah communities in the United States.
  • 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_69d8839270588190886720d9519bbf8f completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b037c5708190ba604e7707b5a8a2 completed April 18, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00a5361c3881909be0fb9b83a59993 completed May 10, 2026, 3:33 p.m.
Created at: April 10, 2026, 5:21 a.m.