Triple

T10322010
Position Surface form Disambiguated ID Type / Status
Subject Sarbadars E242158 entity
Predicate instanceOf P0 FINISHED
Object medieval Iranian state C27852 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: medieval Iranian state
Context triple: [Sarbadars, instanceOf, medieval Iranian state]
  • A. Persianate dynasty
    A Persianate dynasty is a ruling family or political regime that, regardless of its ethnic origin, adopts and promotes Persian language, culture, administrative practices, and aesthetic ideals as the core framework of its governance and elite identity.
  • B. Sasanian client state
    A Sasanian client state was a semi-autonomous polity that retained its own local rulers and internal administration while recognizing the suzerainty of the Sasanian Empire, often providing tribute, military support, and strategic buffer territory.
  • C. Arabian polity
    An Arabian polity is a political entity or state structure that governs a defined territory and population within the Arabian Peninsula or broader Arab world, shaped by regional history, culture, and power relations.
  • D. Islamic empire
    An Islamic empire is a large, multi-ethnic political entity historically governed by Muslim rulers who derive authority from Islamic law and tradition, integrating religious, cultural, and administrative systems across vast territories.
  • E. era in Iranian history
    An era in Iranian history is a distinct period characterized by specific political structures, cultural developments, social dynamics, and major events that collectively define a recognizable phase in the historical evolution of Iran.
  • F. None of above. chosen

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_69d381ac38808190a8ca7457c85b625b completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 11:50 a.m.