Triple

T36662873
Position Surface form Disambiguated ID Type / Status
Subject Mandura woreda E905179 entity
Predicate locatedIn P40 FINISHED
Object Metekel Zone
Metekel Zone is an administrative zone in the Benishangul-Gumuz Region of western Ethiopia, known for its diverse ethnic communities and largely rural, agricultural landscape.
E2196449 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: Metekel Zone | Statement: [Mandura woreda, locatedIn, Metekel Zone]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Metekel Zone
Triple: [Mandura woreda, locatedIn, Metekel Zone]
Generated description
Metekel Zone is an administrative zone in the Benishangul-Gumuz Region of western Ethiopia, known for its diverse ethnic communities and largely rural, agricultural landscape.

Provenance (5 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_69f76e6e3b908190970251b30f76ad71 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7c77e245c8190b46c46be05e7a30c completed May 3, 2026, 10:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a381869e08190ac5623b08418f5a6 completed June 23, 2026, 7:39 a.m.
NEDg Description generation batch_6a3a3f9d07a0819084efaf479549226c completed June 23, 2026, 8:11 a.m.
NED2 Entity disambiguation (via description) batch_6a3a40bf28e48190914b09d7bccae4a6 completed June 23, 2026, 8:15 a.m.
Created at: May 3, 2026, 4:12 p.m.