Triple
T34182359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berta people |
E876855
|
entity |
| Predicate | regionInEthiopia |
P199935
|
FINISHED |
| Object | Benishangul-Gumuz Region |
—
|
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: Benishangul-Gumuz Region | Statement: [Berta people, regionInEthiopia, Benishangul-Gumuz Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionInEthiopia Context triple: [Berta people, regionInEthiopia, Benishangul-Gumuz Region]
-
A.
capitalOfWoreda
Indicates that one location serves as the administrative capital or main town of a specific woreda (district).
-
B.
distanceFromAddisAbaba
Indicates the physical distance between a given location and Addis Ababa.
-
C.
populationRankInEthiopia
Indicates the relative position of an entity in terms of population size compared to other entities within Ethiopia.
-
D.
statusInEthiopia
Indicates the legal, social, or official condition or standing that an entity holds within the context of Ethiopia.
-
E.
borderTypeWithEthiopia
Indicates the specific nature or classification of the border relationship that an entity has with Ethiopia.
- F. None of above. chosen
Provenance (4 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: May 1, 2026, 1:55 a.m.