Triple

T20765161
Position Surface form Disambiguated ID Type / Status
Subject Wolaytta E511075 entity
Predicate hasAlternativeName P39 FINISHED
Object Uolaytta 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: Uolaytta | Statement: [Wolaytta, hasAlternativeName, Uolaytta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uolaytta
Context triple: [Wolaytta, hasAlternativeName, Uolaytta]
  • A. Uolaytta chosen
    Uolaytta is an alternative name for Wolaytta, an Omotic language spoken by the Wolaytta people in southern Ethiopia.
  • B. Laukaa
    Laukaa is a municipality in Central Finland known for its lakes, rural landscapes, and proximity to the city of Jyväskylä.
  • C. Olgossa
    Olgossa is a village in the Darfur region of Sudan, historically known as the birthplace of Saint Josephine Bakhita.
  • D. Halluinois
    Halluinois are the inhabitants or natives of the French commune of Halluin, located in the Nord department near the Belgian border.
  • E. Ojakkala
    Ojakkala is a village in the municipality of Vihti in southern Finland, known for its rural residential character and proximity to the Helsinki metropolitan area.
  • 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.