Triple
T23727953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Pentapolis |
E586331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine duchy |
C47992
|
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 duchy Context triple: [Duchy of Pentapolis, instanceOf, Byzantine duchy]
-
A.
Byzantine client kingdom
A Byzantine client kingdom was a semi-autonomous state that maintained its own local rulers and internal governance while recognizing the suzerainty of the Byzantine Empire, often providing military support, tribute, or political allegiance in exchange for protection and legitimacy.
-
B.
Lombard principality
A Lombard principality is a semi-autonomous medieval political entity ruled by Lombard nobility, typically emerging from the fragmentation of the Lombard Kingdom in Italy and characterized by its own local governance, military, and legal traditions.
-
C.
Piast-ruled principality
A Piast-ruled principality is a medieval territorial polity in Central Europe governed by a member of the Piast dynasty, typically characterized by fragmented authority, hereditary rule, and integration into the broader political landscape of the Polish and neighboring realms.
-
D.
Piast duchy
A Piast duchy is a medieval territorial principality in Poland ruled by a member of the Piast dynasty, typically formed through the partitioning of the Polish kingdom among dynastic heirs.
-
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. 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:08 p.m.