Triple
T8392712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sassanian Armenia |
E197980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Armenian polity |
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: Armenian polity Context triple: [Sassanian Armenia, instanceOf, Armenian polity]
-
A.
medieval Armenian kingdom
A medieval Armenian kingdom is a historically situated political entity in the Armenian Highlands, characterized by Armenian dynastic rule, Christian cultural identity, and feudal socio-political structures interacting with neighboring empires.
-
B.
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.
-
C.
King of Armenia
The King of Armenia is the sovereign ruler of the Armenian kingdom, holding supreme political, military, and ceremonial authority over its territories and people.
-
D.
Sasanian client state
chosen
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.
-
E.
Latin Empire
The Latin Empire was a crusader state established by Western European crusaders after the Fourth Crusade’s conquest of Constantinople in 1204, ruling parts of the former Byzantine Empire until its fall in 1261.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:03 p.m.