Triple
T32574903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubartas Gediminaitis |
E832617
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Lithuanian prince |
C54661
|
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: medieval Lithuanian prince Context triple: [Lubartas Gediminaitis, instanceOf, medieval Lithuanian prince]
-
A.
Lithuanian prince
chosen
A Lithuanian prince is a nobleman of high rank from Lithuania, historically associated with ruling dynasties such as the Grand Duchy of Lithuania, often holding territorial authority, military leadership, and significant political influence.
-
B.
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.
-
C.
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.
-
D.
Lithuanian noble
A Lithuanian noble is a member of the historical aristocratic class of the Grand Duchy of Lithuania (and later the Polish–Lithuanian Commonwealth), holding hereditary titles, land, and political privileges within the region’s feudal and early modern social hierarchy.
-
E.
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.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:04 a.m.