Triple
T24553012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kielce Department |
E607425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | department of the Duchy of Warsaw |
C48439
|
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: department of the Duchy of Warsaw Context triple: [Kielce Department, instanceOf, department of the Duchy of Warsaw]
-
A.
Duke of Warsaw
The Duke of Warsaw is a noble title historically associated with the ruler or high-ranking aristocrat governing the region of Warsaw, often linked to periods of political reorganization in Polish and European history.
-
B.
voivodeship of Poland
A voivodeship of Poland is a top-level administrative region, similar to a province, governed by both elected regional authorities and a centrally appointed governor.
-
C.
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.
-
D.
Silesian duchy
A Silesian duchy is a medieval or early modern territorial principality in the historical region of Silesia, ruled by a duke and often formed through the partition of larger Polish or Bohemian realms.
-
E.
Polish duke
A Polish duke is a high-ranking nobleman in Poland, historically holding significant territorial authority, political influence, and social prestige within the Polish–Lithuanian Commonwealth or earlier Piast and Jagiellonian realms.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:27 a.m.