Triple
T1791486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torwa state |
E39505
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | precolonial African kingdom |
C1185
|
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: precolonial African kingdom Context triple: [Torwa state, instanceOf, precolonial 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.
precolonial African polities
chosen
Precolonial African polities were diverse, locally rooted systems of governance—ranging from centralized kingdoms and empires to decentralized chiefdoms and stateless societies—that organized political authority, economic exchange, and social life across the African continent before European colonial rule.
-
C.
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.
-
D.
maritime kingdom
A maritime kingdom is a sovereign state whose power, economy, and culture are primarily based on seafaring, naval strength, and control of important sea routes and coastal territories.
-
E.
Malay kingdom
A Malay kingdom is a traditional political entity in the Malay world, typically ruled by a sultan or raja, characterized by Malay culture, Islam, and control over regional trade networks.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:32 p.m.