Triple

T14619279
Position Surface form Disambiguated ID Type / Status
Subject Abdirashid Ali Shermarke E343173 entity
Predicate birthPlace P1 FINISHED
Object Hobyo E395015 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: Hobyo | Statement: [Abdirashid Ali Shermarke, birthPlace, Hobyo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hobyo
Context triple: [Abdirashid Ali Shermarke, birthPlace, Hobyo]
  • A. Hobyo chosen
    Hobyo is a historic coastal town and port on the Indian Ocean in central Somalia, known for its strategic location and role in regional trade.
  • B. Hobokan
    Hobokan is an alternative name or spelling for the place or entity known as Hobuck.
  • C. Hobyot
    Hobyot is a rare and severely endangered South Semitic language spoken by small communities in eastern Yemen and western Oman.
  • D. Yoboki
    Yoboki is a small town in Djibouti located within the Dikhil Region, known for its arid landscape and role as a local administrative and trading center.
  • E. Habikino
    Habikino is a city in Osaka Prefecture, Japan, known for its historic kofun burial mounds and role within the Osaka metropolitan area.
  • 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_69d822dffc3c8190aa173b90761bffda completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb46550e48190af45f426f02579bb completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fda924c7308190931c03fbac57b0bf completed May 8, 2026, 9:13 a.m.
Created at: April 10, 2026, 1:25 a.m.