Triple
T2495435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kushan Empire |
E52143
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Asian empire |
C9896
|
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: Central Asian empire Context triple: [Kushan Empire, instanceOf, Central Asian empire]
-
A.
Central Asian polity
A Central Asian polity is a political entity—such as a state, khanate, emirate, or tribal confederation—centered in the Central Asian region, shaped by its steppe geography, Silk Road connections, and interactions among Turkic, Persian, Mongol, and other cultural influences.
-
B.
Central Asian polity
chosen
A Central Asian polity is a historically or contemporarily organized political entity—such as a state, khanate, or empire—centered in the Central Asian region, characterized by its governance structures, territorial control, and interactions with neighboring powers.
-
C.
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.
-
D.
Sultanate
A Sultanate is a form of monarchy or state ruled by a sultan, typically characterized by Islamic governance traditions and varying degrees of centralized authority.
-
E.
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.
- 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_69ab4955111c8190835bf619adec21ff |
completed | March 6, 2026, 9:38 p.m. |
Created at: March 6, 2026, 9:45 p.m.