Triple
T30000645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidama Region |
E762156
|
entity |
| Predicate | partOfHighland |
P165213
|
FINISHED |
| Object | Ethiopian Highlands |
—
|
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: Ethiopian Highlands | Statement: [Sidama Region, partOfHighland, Ethiopian Highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfHighland Context triple: [Sidama Region, partOfHighland, Ethiopian Highlands]
-
A.
isHighlandLandmarkFor
Indicates that a landmark is recognized as a notable or defining feature specifically within a highland area or region.
-
B.
isInHighlandRegion
chosen
Indicates that an entity is located within a highland or elevated geographic region.
-
C.
isHighlandConstituency
Indicates that a given constituency is located within or classified as part of the Highland region.
-
D.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
E.
isCroftingArea
Indicates that a given geographic area is designated or recognized as a crofting area, where crofting (small-scale agricultural tenancy) is permitted or regulated.
- F. None of above.
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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
Created at: April 29, 2026, 6:41 p.m.