Triple

T16442932
Position Surface form Disambiguated ID Type / Status
Subject Gedo E399348 entity
Predicate hasBorderTown P847 FINISHED
Object Beled Hawo E1212952 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: Beled Hawo | Statement: [Gedo, hasBorderTown, Beled Hawo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beled Hawo
Context triple: [Gedo, hasBorderTown, Beled Hawo]
  • A. Beled Hawo chosen
    Beled Hawo is a border town in southwestern Somalia that serves as a key commercial and transit hub between Somalia, Kenya, and Ethiopia.
  • B. Harar
    Harar is a historic fortified city in eastern Ethiopia renowned for its ancient Islamic heritage, distinctive city walls, and status as a UNESCO World Heritage Site.
  • C. Gafat
    Gafat is an extinct South Ethio-Semitic language once spoken in parts of Ethiopia.
  • D. Birr
    Birr is a historic town in County Offaly, Ireland, known for Birr Castle, its demesne, and its role in early astronomical research.
  • E. Birr
    Birr is a municipality in the canton of Aargau in northern Switzerland, known for its residential character and proximity to major transport routes and industrial centers.
  • 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_69d87f2c6778819080fcfae53be8f12a completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32cd8d2988190acb5722a15623319 completed April 18, 2026, 7:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f4b738881908f8a205466397f33 completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:10 a.m.