Triple
T29061315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Švitrigaila |
E735543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Gediminid dynasty |
C26535
|
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: member of the Gediminid dynasty Context triple: [Švitrigaila, instanceOf, member of the Gediminid dynasty]
-
A.
Gediminid dynasty member
chosen
A Gediminid dynasty member is an individual descended from or belonging to the medieval ruling house founded by Grand Duke Gediminas, which governed the Grand Duchy of Lithuania and its successor states.
-
B.
Jagiellonian dynasty member
A Jagiellonian dynasty member is an individual belonging to the royal house that ruled parts of Central and Eastern Europe, including Poland, Lithuania, Bohemia, and Hungary, from the late 14th to the 16th century.
-
C.
member of the Rurik dynasty
A member of the Rurik dynasty is an individual belonging to the medieval ruling family traditionally traced to the Varangian prince Rurik, which governed parts of Eastern Europe, including Kievan Rus and later principalities, from the 9th to the 16th centuries.
-
D.
Piast dynasty member
A Piast dynasty member is an individual belonging to the first historical ruling dynasty of Poland, which governed various Polish and regional territories from the 10th to the 14th century (and in some branches beyond).
-
E.
Bagrationi dynasty member
A Bagrationi dynasty member is an individual belonging to the historic royal family that ruled Georgia and related Caucasian realms for centuries, often holding titles of kings, princes, or nobles.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:15 a.m.