Triple
T25222394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mon kingdoms |
E631998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-modern kingdom |
C35232
|
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: pre-modern kingdom Context triple: [Mon kingdoms, instanceOf, pre-modern kingdom]
-
A.
pre-colonial kingdom
A pre-colonial kingdom is a sovereign political entity that existed before foreign colonial rule, typically characterized by indigenous governance structures, distinct cultural traditions, and control over defined territories and populations.
-
B.
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.
-
C.
early medieval kingdom
An early medieval kingdom is a territorially bounded, monarch-led polity emerging after the fall of the Western Roman Empire, characterized by decentralized power, personal lordship ties, and a fusion of Roman, Germanic, and Christian traditions.
-
D.
pre-colonial African kingdom
chosen
A pre-colonial African kingdom is a sovereign, territorially defined polity that existed in Africa before European colonial rule, characterized by its own systems of governance, economy, culture, and social organization.
-
E.
early modern state
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 1:03 p.m.