Triple
T16858305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michał Korybut Wiśniowiecki |
E409845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish–Lithuanian monarch |
C8561
|
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: Polish–Lithuanian monarch Context triple: [Michał Korybut Wiśniowiecki, instanceOf, Polish–Lithuanian monarch]
-
A.
King of Poland
chosen
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.
-
B.
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.
-
C.
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.
-
D.
monarch of Galicia–Volhynia
The monarch of Galicia–Volhynia was the sovereign ruler of the medieval East Slavic kingdom of Galicia–Volhynia, exercising supreme political, military, and judicial authority over its territories and subjects.
-
E.
Polish prince
A Polish prince is a male member of the historical Polish nobility or royal family, often holding hereditary titles, lands, and political influence within the Polish–Lithuanian Commonwealth or its predecessor states.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
Created at: April 10, 2026, 5:24 a.m.