Triple

T1698807
Position Surface form Disambiguated ID Type / Status
Subject Nogai Horde E36721 entity
Predicate instanceOf P0 FINISHED
Object Turkic-Mongol polity 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: Turkic-Mongol polity
Context triple: [Nogai Horde, instanceOf, Turkic-Mongol polity]
  • A. Central Asian polity chosen
    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
    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. 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.
  • D. 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.
  • E. East Slavic polity
    An East Slavic polity is a historically or contemporarily organized political entity—such as a state, principality, or federation—primarily inhabited and shaped by East Slavic peoples and their cultural, linguistic, and religious traditions.
  • 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_69a886163dec8190859c514232a37a05 completed March 4, 2026, 7:20 p.m.
Created at: March 4, 2026, 7:30 p.m.