Triple
T3227511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ögedei Khan |
E67659
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Great Khan of the Mongol Empire |
C7346
|
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: Great Khan of the Mongol Empire Context triple: [Ögedei Khan, instanceOf, Great Khan of the Mongol Empire]
-
A.
Mongol ruler
chosen
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.
Grand Prince of Moscow
The Grand Prince of Moscow was the medieval ruler of the Grand Duchy of Moscow, who gradually consolidated Russian lands, led resistance against foreign domination, and laid the foundations for a centralized Russian state.
-
C.
Inca emperor
The Inca emperor was the supreme political, religious, and military ruler of the Inca Empire, regarded as a divine descendant of the sun god Inti who governed from the capital of Cusco.
-
D.
Emperor of India
The "Emperor of India" was a sovereign title used by the British monarch from 1876 to 1948 to signify their supreme imperial authority over the territories of the Indian subcontinent under British rule.
-
E.
Inca ruler
An Inca ruler was the supreme political, religious, and military leader of the Inca Empire, believed to be a divine descendant of the sun god Inti and responsible for governing its vast territories and people.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:08 p.m.