Triple
T2107335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aksumite Empire |
E42424
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient African kingdom |
C4987
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ancient African kingdom Context triple: [Aksumite Empire, instanceOf, ancient African kingdom]
-
A.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
B.
ancient empire
chosen
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
-
C.
ancient Egyptian city
An ancient Egyptian city is an urban settlement along the Nile characterized by monumental temples and tombs, administrative and residential districts, and a society organized around pharaonic rule, religion, and agriculture.
-
D.
pre-Columbian city-state
A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
-
E.
country in Central Africa
A country in Central Africa is a sovereign state located in the central region of the African continent, typically characterized by diverse ethnic groups, tropical or equatorial climates, and economies often based on natural resources and agriculture.
- F. None of above.
Provenance (1 batch)
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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:43 p.m.