Triple

T14786404
Position Surface form Disambiguated ID Type / Status
Subject Kafa language E347536 entity
Predicate alternateName P39 FINISHED
Object Kaffa E386663 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: Kaffa | Statement: [Kafa language, alternateName, Kaffa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kaffa
Context triple: [Kafa language, alternateName, Kaffa]
  • A. Kafa chosen
    Kafa is an Omotic language spoken primarily in southwestern Ethiopia by the Kafa people.
  • B. Caffa
    Caffa is the historical name of the Crimean port city now known as Feodosia, which was a major Genoese trading colony and a key Black Sea commercial hub in the Middle Ages.
  • C. Caffee Oromia
    Caffee Oromia is the regional parliament of Ethiopia’s Oromia Region, responsible for making laws and overseeing the regional government.
  • D. Kaffa Zone
    Kaffa Zone is an administrative area in southwestern Ethiopia known as the historic homeland of the Kaffa people and as one of the regions associated with the origin of coffee.
  • E. Sidamo
    Sidamo is a Cushitic language spoken primarily in southern Ethiopia by the Sidama people.
  • 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_69d822e9b9e08190bedcc31a163fda82 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decaa083e481908336d58d026eec32 completed April 14, 2026, 11:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe388fc0e08190a758a1e0a4140909 completed May 8, 2026, 7:25 p.m.
Created at: April 10, 2026, 1:31 a.m.