Triple
T35319003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolesław III the Generous |
E1019984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Legnica |
C13805
|
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: Duke of Legnica Context triple: [Bolesław III the Generous, instanceOf, Duke of Legnica]
-
A.
Duke of Kraków
The Duke of Kraków is a medieval Polish noble title denoting the ruler of the Kraków region, often associated with senior authority among the Piast dukes.
-
B.
Duke of Sandomierz
The Duke of Sandomierz was a medieval Polish noble title denoting the ruler of the Sandomierz region, often held by members of the Piast dynasty as part of the fragmented Polish kingdom.
-
C.
Duke of Sieradz
The Duke of Sieradz was a medieval Polish noble title denoting the ruler of the Sieradz region, often held by members of the Piast dynasty during the period of Poland’s territorial fragmentation.
-
D.
Duke of Danzig
The Duke of Danzig is a noble title historically associated with the governance, representation, or symbolic lordship over the city and surrounding region of Danzig (modern-day Gdańsk), often reflecting shifting political control in Central and Eastern Europe.
-
E.
Polish duke
chosen
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.
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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.