Triple
T14468778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Silesia |
E358782
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Piast-ruled principality |
C34820
|
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: Piast-ruled principality Context triple: [Duchy of Silesia, instanceOf, Piast-ruled principality]
-
A.
Russian principality
A Russian principality is a semi-autonomous medieval or early modern territorial state ruled by a prince within the broader political and cultural sphere of Rus', often owing allegiance to a grand prince or tsar.
-
B.
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.
-
C.
medieval East Slavic state
A medieval East Slavic state is a historically situated political entity formed by East Slavic peoples between the 9th and 15th centuries, characterized by princely rule, Orthodox Christianity, and a feudal socio-economic structure.
-
D.
Bulgarian principality
A Bulgarian principality is a semi-autonomous, monarchical political entity historically established on Bulgarian territory, typically under the suzerainty or influence of a larger empire or state.
-
E.
Armenian principality
An Armenian principality is a semi-autonomous political entity historically governed by Armenian nobility, exercising regional authority under varying degrees of dependence on larger empires or kingdoms.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.