Triple
T22601597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altan Khan |
E574834
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol leader |
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: Mongol leader Context triple: [Altan Khan, instanceOf, Mongol leader]
-
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.
Genghis Khan general
A Genghis Khan general is a high-ranking military commander serving under Genghis Khan, responsible for leading Mongol armies, executing strategic campaigns, and enforcing the Khan’s authority across conquered territories.
-
C.
Turkic military leader
A Turkic military leader is a commander of Turkic origin who organizes, directs, and leads armed forces in warfare, defense, or expansion, often shaping the political and cultural trajectory of Turkic societies.
-
D.
Jurchen chieftain
A Jurchen chieftain is a hereditary or militarily ascendant leader of a Jurchen tribal group who exercises political, military, and economic authority within the broader context of Northeast Asian steppe-forest societies.
-
E.
Mongol noble
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 2:50 p.m.