Triple

T20765365
Position Surface form Disambiguated ID Type / Status
Subject Gamo language E511080 entity
Predicate hasNativeSpeakersIn P5231 FINISHED
Object Gamo Zone NE NERFINISHED

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: Gamo Zone | Statement: [Gamo language, hasNativeSpeakersIn, Gamo Zone]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gamo Zone
Context triple: [Gamo language, hasNativeSpeakersIn, Gamo Zone]
  • A. Gamo Zone chosen
    Gamo Zone is an administrative zone in southern Ethiopia, named after the Gamo people and known for its diverse highland landscapes and cultural heritage.
  • B. Gamo
    Gamo is an Omotic language spoken primarily by the Gamo people in southwestern Ethiopia.
  • C. Gamzatti
    Gamzatti is the proud and aristocratic daughter of the Rajah and rival to the temple dancer Nikiya in the classical ballet *La Bayadère*.
  • D. Gamu
    Gamu is a landlocked agricultural municipality in the province of Isabela in the Cagayan Valley region of the Philippines.
  • E. Jasso
    Jasso is a locality in the Mexican state of Hidalgo, likely known as an industrial or residential community within the region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4ca01148190ac018e57e0cab46f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c24bde0c8190b46986b89bf2e037 completed April 21, 2026, 12:18 a.m.
Created at: April 16, 2026, 12:36 p.m.