Triple

T9389451
Position Surface form Disambiguated ID Type / Status
Subject Triqui language E225987 entity
Predicate hasDialect P4251 FINISHED
Object Copala Triqui E195261 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: Copala Triqui | Statement: [Triqui language, hasDialect, Copala Triqui]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Copala Triqui
Context triple: [Triqui language, hasDialect, Copala Triqui]
  • A. Trique chosen
    Trique is an indigenous Mesoamerican language spoken in Oaxaca, Mexico, known for its complex tonal system and belonging to the Oto-Manguean language family.
  • B. Cha’palaachi
    Cha’palaachi is the indigenous language spoken by the Chachi people of Ecuador’s coastal and northwestern rainforest regions.
  • C. Campechuela
    Campechuela is a coastal municipality and town in southeastern Cuba known for its agricultural activities within Granma Province.
  • D. Tejipió
    Tejipió is a neighborhood in the city of Recife, Brazil, known as part of the urban fabric of the state capital of Pernambuco.
  • E. Choachí
    Choachí is a mountainous municipality in the Cundinamarca Department of Colombia, known for its cool climate, natural landscapes, and proximity to Bogotá.
  • 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_69ca842f7e3481908bf5bcf52e032dbd completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd50d83c188190925c389dff1341b0 completed April 1, 2026, 5:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69d100f86bac8190a26ab156f24455bb completed April 4, 2026, 12:15 p.m.
Created at: March 30, 2026, 7:45 p.m.