Triple

T15945418
Position Surface form Disambiguated ID Type / Status
Subject Sidamu Afoo E386670 entity
Predicate hasEthnologueEntry P19233 FINISHED
Object Sidamo E82602 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: Sidamo | Statement: [Sidamu Afoo, hasEthnologueEntry, Sidamo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sidamo
Context triple: [Sidamu Afoo, hasEthnologueEntry, Sidamo]
  • A. Sidamo chosen
    Sidamo is a Cushitic language spoken primarily in southern Ethiopia by the Sidama people.
  • B. Caffee Oromia
    Caffee Oromia is the regional parliament of Ethiopia’s Oromia Region, responsible for making laws and overseeing the regional government.
  • C. 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.
  • D. Arabica
    Arabica is a high-quality coffee species prized for its smooth, aromatic flavor and widely used in premium coffee varieties worldwide.
  • E. Kafa
    Kafa is an Omotic language spoken primarily in southwestern Ethiopia by the Kafa 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_69d86da882448190a82ea962fe343b79 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156d0d55c8190af59ff169e8add78 completed April 16, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffbe76df6481909f8246099faa377a completed May 9, 2026, 11:08 p.m.
Created at: April 10, 2026, 4:53 a.m.