Triple
T2186463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol Ilkhanate |
E49163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | successor state of the Mongol Empire |
C5657
|
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: successor state of the Mongol Empire Context triple: [Mongol Ilkhanate, instanceOf, successor state of the Mongol Empire]
-
A.
Mongol ruler
A Mongol ruler is a sovereign leader of the Mongol people and their empire, wielding military, political, and often spiritual authority over vast, multiethnic territories.
-
B.
subah of the Mughal Empire
A subah of the Mughal Empire was a major provincial administrative division governed by a subahdar, responsible for local governance, revenue collection, and military control within its territory.
-
C.
vassal state
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
D.
successor state
chosen
A successor state is a new system configuration that directly results from applying a specific action or transition to a current state within a defined process or model.
-
E.
Crusader state
A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:45 p.m.