Triple
T3452873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leszek II the Black |
E72832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Piast duke |
C12762
|
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 duke Context triple: [Leszek II the Black, instanceOf, Piast duke]
-
A.
Grand Duke of Lithuania
The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions with neighboring states.
-
B.
Grand Duke of Lithuania
The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions and alliances with neighboring states.
-
C.
King of Poland
The King of Poland was the sovereign ruler of the Polish state, historically elected by the nobility and responsible for governing the kingdom, leading its armies, and representing it in foreign affairs.
-
D.
King of Poland
The King of Poland was the sovereign ruler of the Polish state, historically elected by the nobility and responsible for governing the kingdom, leading its military, and representing it in foreign affairs.
-
E.
King in Prussia
King in Prussia was the royal title used by the Hohenzollern rulers of Brandenburg-Prussia from 1701 to 1772, signifying their kingship over Prussia while remaining nominally subordinate to the Holy Roman Emperor within the empire.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:16 p.m.