Triple
T8223396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nogai Khan |
E192119
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mongol military 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 military leader Context triple: [Nogai Khan, instanceOf, Mongol military 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.
Timurid ruler
A Timurid ruler is a sovereign from the Timurid dynasty (14th–16th centuries) who governed territories in Central Asia, Iran, and surrounding regions, often noted for military conquest, Persianate court culture, and patronage of arts and architecture.
-
C.
medieval military leader
A medieval military leader is a high-ranking commander responsible for organizing, directing, and inspiring armed forces in warfare during the Middle Ages, often balancing battlefield tactics with feudal, political, and religious obligations.
-
D.
19th-century military leader
A 19th-century military leader is a high-ranking commander who directed armed forces during the 1800s, shaping national and imperial conflicts through strategic planning, battlefield leadership, and political influence.
-
E.
Ottoman general
An Ottoman general is a high-ranking military commander in the Ottoman Empire responsible for planning, leading, and overseeing major military campaigns and the administration of troops.
- 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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:45 p.m.