Triple

T5285901
Position Surface form Disambiguated ID Type / Status
Subject Lazica E119617 entity
Predicate instanceOf P0 FINISHED
Object Sasanian client state C18316 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: Sasanian client state
Context triple: [Lazica, instanceOf, Sasanian client 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. client state of the Roman Empire
    A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
  • C. South Arabian kingdom
    A South Arabian kingdom is an ancient political entity that arose in the southern Arabian Peninsula, characterized by complex social structures, trade-based economies, and distinctive cultural and religious practices.
  • D. 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.
  • E. Crusader state
    A Crusader state is a feudal polity established by Western European crusaders in the Eastern Mediterranean and surrounding regions during the medieval Crusades, maintained through military, religious, and political control over conquered territories.
  • 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_69bd446de5648190b313a90bd96730d2 completed March 20, 2026, 12:58 p.m.
Created at: March 20, 2026, 1:52 p.m.