Triple
T6367093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol Empire |
E143254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eurasian empire |
C20267
|
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: Eurasian empire Context triple: [Mongol Empire, instanceOf, Eurasian empire]
-
A.
ancient empire
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.
-
B.
dynastic empire
A dynastic empire is a vast, centralized state ruled over generations by a single family lineage that legitimizes its authority through hereditary succession and often divine or traditional claims to power.
-
C.
imperial state of the Holy Roman Empire
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
-
D.
colonial empire
A colonial empire is a political and economic system in which a dominant state controls and exploits distant territories and their populations, typically through settlement, resource extraction, and imposed governance.
-
E.
imperial confederation
An imperial confederation is a loose union of semi-autonomous states or territories under the overarching authority of an empire, which coordinates common policies while allowing substantial local self-rule.
- F. None of above. chosen
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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:32 p.m.