Triple

T18618705
Position Surface form Disambiguated ID Type / Status
Subject Shewa E455094 entity
Predicate historicalCapital P2536 FINISHED
Object Debre Berhan 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: Debre Berhan | Statement: [Shewa, historicalCapital, Debre Berhan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Debre Berhan
Context triple: [Shewa, historicalCapital, Debre Berhan]
  • A. Debre Birhan chosen
    Debre Birhan is a historic highland city in central Ethiopia known for its cool climate, religious heritage, and role as a regional center in the Amhara Region.
  • B. Debre Tabor
    Debre Tabor is a historic town in northern Ethiopia that once served as a royal residence and political center during the 19th century.
  • C. Yirgalem
    Yirgalem is a town in southern Ethiopia known for its coffee-growing region and lush, forested surroundings.
  • D. Bete Meskel
    Bete Meskel is one of the rock-hewn churches in the Lalibela complex of Ethiopia, noted for its religious significance and distinctive monolithic architecture.
  • E. Senafe
    Senafe is a town in southern Eritrea known for its strategic location near the Ethiopian border and its surrounding highland landscapes.
  • 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_69d8d38bbe7c8190bdec3138e7d413c9 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54d07dc288190bb3b8b5ab06518da completed April 19, 2026, 9:45 p.m.
Created at: April 10, 2026, 11:46 a.m.