Triple
T22438109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ghassanids |
E554679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine client kingdom |
C46282
|
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: Byzantine client kingdom Context triple: [Ghassanids, instanceOf, Byzantine client kingdom]
-
A.
Byzantine successor state
A Byzantine successor state is a political entity that emerged from the fragmentation of the Byzantine Empire, claiming continuity with its imperial, cultural, and religious traditions.
-
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.
Turkish principality
A Turkish principality is a semi-independent, territorially defined political entity ruled by a Turkish dynastic leader, typically emerging in the medieval or early modern period within the broader context of Turkic state formation and regional power dynamics.
-
D.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
-
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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:47 p.m.