Triple
T28788310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konstanty Ostrogski |
E726879
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Grand Hetman of Lithuania |
C54937
|
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: Grand Hetman of Lithuania Context triple: [Konstanty Ostrogski, instanceOf, Grand Hetman of Lithuania]
-
A.
Grand Hetman of the Crown
The Grand Hetman of the Crown was the highest-ranking military commander of the Crown of the Kingdom of Poland in the Polish–Lithuanian Commonwealth, responsible for leading its armed forces and overseeing military affairs.
-
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 with neighboring states.
-
C.
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.
-
D.
High Duke of Poland
The High Duke of Poland was the senior prince who, under the 12th–13th century Piast succession system, held supreme authority over the Polish realm and its subordinate duchies.
-
E.
King of Lithuania
The King of Lithuania is the sovereign monarch who historically ruled the Grand Duchy of Lithuania, holding supreme political, military, and symbolic authority over its territories and people.
- 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:22 a.m.