Triple

T33879834
Position Surface form Disambiguated ID Type / Status
Subject Bole area, Addis Ababa E868453 entity
Predicate near P350 FINISHED
Object Kazanchis area
Kazanchis area is a central district in Addis Ababa known for its concentration of hotels, offices, and proximity to major business and diplomatic centers.
E2072406 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: Kazanchis area | Statement: [Bole area, Addis Ababa, near, Kazanchis area]
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: Kazanchis area
Triple: [Bole area, Addis Ababa, near, Kazanchis area]
Generated description
Kazanchis area is a central district in Addis Ababa known for its concentration of hotels, offices, and proximity to major business and diplomatic centers.

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_69f34995b81c8190acdb45cea5a10eff completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7010881908190b7942ee7ee731537 completed May 3, 2026, 8:02 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36762e286081908cbcd6a834a6b310 completed June 20, 2026, 11:14 a.m.
NEDg Description generation batch_6a367a55dc008190bf0cccf0ba04d98d completed June 20, 2026, 11:32 a.m.
NED2 Entity disambiguation (via description) batch_6a367ade4ea081909db631779baaf658 completed June 20, 2026, 11:34 a.m.
Created at: May 1, 2026, 1:48 a.m.