Triple

T37199395
Position Surface form Disambiguated ID Type / Status
Subject Kindah kingdom E921686 entity
Predicate instanceOf P0 FINISHED
Object pre-Islamic Arab polity C20121 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: pre-Islamic Arab polity
Context triple: [Kindah kingdom, instanceOf, pre-Islamic Arab polity]
  • A. Arabian polity chosen
    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.
  • B. Syro-Aramean polity
    A Syro-Aramean polity is a historical or conceptual political entity rooted in the cultural, linguistic, and territorial interplay of ancient Syrian and Aramean societies in the Near East.
  • C. pre-modern polity
    A pre-modern polity is a historically situated political entity—such as a city-state, kingdom, or empire—whose governance, social order, and legitimacy are structured primarily through kinship, religion, customary law, and personal rule rather than modern bureaucratic, territorial, and legal-rational institutions.
  • D. sub-Roman polity
    A sub-Roman polity is a regional political entity that emerged in former Western Roman territories, blending residual Roman institutions with local or incoming non-Roman power structures during the transitional period after imperial collapse.
  • E. pre-colonial kingdom
    A pre-colonial kingdom is a sovereign political entity that existed before foreign colonial rule, typically characterized by indigenous governance structures, distinct cultural traditions, and control over defined territories and populations.
  • 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_69f76ea313a08190a54404cd1e47da90 completed May 3, 2026, 3:49 p.m.
Created at: May 3, 2026, 4:15 p.m.